Sometimes, jQuery with its plugins in webpack could be a real hassle, especially when you are not familiar with webpack, or something wrong under the hood. I would suggest that for faster development time, move jQuery to global (from script tag usage), and later try to move it back to the bundle if needed.
For your scenario, it would mean something like this:
im kind of late to frontend development (joined after when jQuery was the thing).
What´s wrong with importing 3rd-party libs anyway - besides global namespace and no treeshaking / importing only stuff one really needs.
Just curious…
There’s nothing wrong with jQuery at all. I was only suggesting an option to minimize the number of things to need to juggle at once to get the dev workflow smooth at first. If I remember correctly, jQuery supports UMD module format, which means you won’t leak jQuery into global, if the build is configured properly