Do you write code differently when you’re working on a personal project versus when you’re writing for work or another project that may one day be someone else’s responsibility? If you don’t, have you considered if you should? Because the answer is probably yes, you should.
We all have code idiosyncracies, habits, odd patterns or even non-standard tools that we like to use. For personal projects that aren’t going anywhere, that’s fine. In fact it’s good and healthy to play around with new, up and coming tools. But when you’re working in a production environment, especially developing a codebase that is meant to last for years, adhering to standards and prioritizing readability is a must.
The real answer is your codebase should be consistent. If you choose to use jQuery (or choose not to), be consistent throughout your codebase. As long as you’re only asking future developers to learn and work with a standardized set of tools, it’s not an onerous proposition. As much as possible, make sure those tools are also industry standards as well. This will not only improve the day to day life of your developers, but make hiring and training less daunting as well.