You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a webpack user, I'm unable to use this plugin without hacking the functions.
When using webpack to bundle jQuery and, ie, Bootstrap JS together one has to deregister WordPress's own jQuery and register webpack's manifest.js, vendor.js (which is where jQuery is residing), and app.js (user scripts).
However, this plugin places its front.js above vendor.js which throws an error in the inspector console that jQuery isn't loaded.
Either the plugin must be modified to take this into account and either check if vendor is enqueued instead, force-place itself below other enqueues, or the check for jQuery must be removed (which is sort of counter-productive).
The text was updated successfully, but these errors were encountered:
[...] one has to deregister WordPress's own jQuery [...]
[...] this plugin places its front.js above vendor.js which throws an error in the inspector console that jQuery isn't loaded.
This is rather strange, because the plugin enqueues front.js with jQuery as dependency, so if you deregister jQuery properly then front.js should not be enqueued at all...
If you are already deregistering jQuery, why not to deregister plugin's front.js as well and register it with your vendor.js as dependency?
As a webpack user, I'm unable to use this plugin without hacking the functions.
When using webpack to bundle jQuery and, ie, Bootstrap JS together one has to deregister WordPress's own jQuery and register webpack's
manifest.js
,vendor.js
(which is where jQuery is residing), andapp.js
(user scripts).However, this plugin places its
front.js
abovevendor.js
which throws an error in the inspector console that jQuery isn't loaded.Either the plugin must be modified to take this into account and either check if
vendor
is enqueued instead, force-place itself below other enqueues, or the check for jQuery must be removed (which is sort of counter-productive).The text was updated successfully, but these errors were encountered: