- Issue created by @colan
- 🇨🇦Canada smulvih2 Canada 🍁
Hey Colan, thanks for bringing this up! WxT 5.4.x uses wet-boew 4.0.75, and 6.1.x uses wet-boew 4.0.85, where these libraries are no longer bundled.
This change prevents wet-boew JS from loading, so not a good change to add to wxt_bootstrap, although fine to use in your case if wet-boew is not needed. You could also disable wxt_library to prevent that library from loading in the first place. Could also update wet-boew in your composer.json file like this:
"require": { "wet-boew/wet-boew": "4.0.85 as 4.0.75" }
Will be publishing 6.1.x shortly this week/weekend, just running through upgrade path testing.
- 🇨🇦Canada colan Toronto 🇨🇦
Thanks for the tip, but it looks like they weren't removed after running this, `ddev composer install`, clearing caches, and then reloading the page:
ddev composer require "wet-boew/wet-boew:4.0.85 as 4.0.75"
Not getting `undefined` when running these in the browser console:
typeof Modernizr
typeof yepnope
So we'll stick with the big removal for now, unless there's a better option.
- 🇨🇦Canada colan Toronto 🇨🇦
@smulvih2: I'm reopening this because you may not see it otherwise.
It turns out we are using some of this stuff so still need it.
Upgrading `web-boew` did not remove the libraries. Could there be a bug there that's allowing these 2 libraries to still show up?