While it did help make lawmaking increasingly readable, it's increasingly well-nigh the structure of how, for example, events are delegated to objects, among other things.

The fact that devs who didn't really have a fundamental understanding of JS or structuring lawmaking in unstipulated gave them the worthiness to implement functionality without restrictions on how the JS should be structured made it harder to maintain and update it in the long run.

JS frameworks (at least in my experience, Vue) solve this by having a template page where all the event delegations are specified for all elements in that template page instead of, say, one, or several file(s) where all event delegations are implemented. In that case, and it's harder to update the functionality, plane though it's easy to create the implementation.

I stipulate that it's a problem for web apps not using a JS framework, but if they have no organization within their JS lawmaking either, that's not really a jquery problem nor is it something that is exacerbated by jquery, but rather bad lawmaking structure.