It’s been awhile since I did any frontend work. Is there something that has taken jQuery’s place?

  • Kissaki@feddit.deEnglish
    68·
    1 year ago

    JavaScript itself provides the functionality jQuery became popular for. So no. Check the standard lib first before considering helper libs.

  • Max-P@lemmy.max-p.me
    31·
    1 year ago

    It depends what you want to do and the amount of polyfills/backwards compatibility you need.

    Nowadays most projects use one of the big frameworks like React/Vue/Svelte and others which take a vastly different approach to maintaining the DOM and for the most part you never manipulate nodes yourself, therefore you don’t need jQuery and it’s not used much anymore. JSX is weird at first but it’s actually quite nice. Some of those libraries like SolidJS have impressively low overhead.

    And for those that like to stick to just minimal JS, the browser APIs have matured a lot so a lot of jQuery isn’t really necessary anymore either. We have querySelectorAll and things like Array.prototype.forEach and Array.prototype.map and arrow functions that cut down a lot on what shortcuts jQuery would offer. Visual effects are usually done with CSS animations and just switching up classes. Everything AJAX is easier and cleaner with the new fetch() function and accessories. Vanilla JavaScript is for the most part quite usable and easy these days. You can even create custom HTML elements from JavaScript to make your life easier!

    But if you’re looking at the jQuery API specifically, you can still use jQuery today. It’s still maintained and functional. I think modern versions are pretty small too since it no longer needs half of it to be Internet Explorer hacks and other obsolete browsers that were holding web development back.

  • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
    14·
    1 year ago

    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

    • Nerd02@lemmy.basedcount.comEnglish
      6·
      1 year ago

      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?

      • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
        5·
        1 year ago

        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

  • taaz@biglemmowski.winEnglish
    142·
    1 year ago

    No, because the current practices have shifted from writing html+css+js in the classic style to using JavaScript frontend frameworks like vue, react, angular, svelte… Which offer a lot of features that would jQyery give you but also removed the need for some of them.
    The paradigm has shifted and I don’t think jQuery is used anymore (atleast not for new projects).

  • pe1uca@lemmy.pe1uca.dev
    11·
    1 year ago

    IIRC most stuff can be done with vanilla JS in any modern browser.
    Although, I’ve been doing little front-end work, and mostly for personal projects, nothing fancy nor production ready, so someone might have another opinion about using jQuery.