Require jQuery

@zedna – Sorry to hear that. To be honest, I’m not sure its a fair assessment. I’m sure you are aware that WordPress itself loads jQuery by default on every page of the site. Pretty safe bet for 99.999% of sites on WP that it will already be there. ANd I know you might say but what about static JS or headless, well those wouldn’t even account for 0.001% of WP sites still, so may be unreasonable to think a plugin meant to work within this ecosystem shouldn’t use the tools & code already included rather than including their own extra logic to handle those things.

You are actually the first person I’ve seen make such a complaint for any plugin, but I understand the sentiment.

Just so happens we are already working toward removing all dependencies over time that aren’t packaged via our webpack builds. Actually multiple issues on our github for that, including jQuery. Already removed several like jQuery cookie.

That said the main reason we still use jQuery is the UI positioning library. We haven’t found a decent GPL library that can handle things as well as jQuery UI due to the wide variety of options we provide to position & animate the popups. So likely we are rewriting that entire logic from scratch, which is not exactly high priority for a dev team of 1, supporting 600k websites haha.

Hopefully you can see our position and update the stars. Appreciate the feedback either way.

PS, as a developer, I’d be interested to hear your thoughts. We would never write it in Vanilla JS, why would anyone duplicate so much work, with so many great open source libraries out there via NPM packages, you just wouldn’t know that they were loaded unless you inspected our bundled js.

If that is a truly a requirement, serious question, why use WP at all? Everything from WooCommerce to Events Calendar plugins use jQuery to great extent.

+1 for Vanilla JS

@ecomturbo – Would love an elaboration, do you mean no dependence on jQuery, or no dependence at all. The latter is unreasonable and for purists (read self sadists just trying to prove they can). Its neither efficient or scalable in practice. The boilerplate to make some things work in all browsers alone would be ridiculous overhead to manage for just a few of the functionalities we rely on.

We are however and have been for some time already moving away from jQuery. Just takes time as an extremely small dev team, when 600k sites are using your product already, and you don’t want to induce extra support loads with sudden breaking changes. But give us time.