Yes they forgot to include all of the 'non updated' files in the 2.0 version. I am going to have to apply a patch to the 1.0 version, I'll see if I can post it here after I get it working.
I found this in the merge requests, uploading here for other users.
- 🇺🇸United States bburg Washington D.C.
Yeah, I'm not really sure how the 2.0.0 version of the module is supposed to function if it no longer has a libraries file.
The patch in #4 doesn't seem to include all of the missing files, so I created a new one that re-adds them here. I have no idea if it's adequate to use for updating to 2.0 of the module.
- 🇨🇭Switzerland Berdir Switzerland
That's because they are defined by the jquery_ui module already (dynamically), but the name does have changed I guess.
- 🇺🇸United States DamienMcKenna NH, USA
There needs to be some official documentation about this somewhere as it's extremely confusing.
- 🇺🇸United States DamienMcKenna NH, USA
Apparently the jQuery 8.x-1.5 → release completely changed how the libraries were loaded, though the release notes don't reference an issue where more details could have been found. Very few people noticed because 8.x-1.6 → was released the next day, and its release notes don't mention anything about the functionality change.
I opened ✨ Remove the need for the submodules Active because the current process is a bit of a confusing mess.