72
Is jQuery still the go-to JS helper library?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Dec 2023
72 points (97.4% liked)
Programming
17314 readers
106 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
A lot of jQuery's features are now available in native JS - would also suggest just using native JS anyway because jQuery won't throw any errors into the console if a selector matches no elements etc.
The only additional library I've needed recently for (personal work) is Axios for requests - easier than working with the Fetch API in some cases
May I ask what cases? I used to use Axios on Node, before they implemented the fetch API over there but I haven't touched it since. And defintiely never used it on the client. Could you make an example of some case where it'd be easier to work with Axios than with fetch?
For me it's the ability to set up a shared instance with the base request URL, and set headers for things like the user's token, allowing all requests made with that shared Axios instance to be sent to the right path with the token without needing to define them for each individual request.
To be honest though something similar can be done with spread syntax in the Fetch API's options parameter