postcss-nested VS jQuery

And we have to make sure that it runs before the nesting plugin, otherwise it will not work at all due to an issue when using both plugins together.

postcss-nested

What you're describing is nesting, which is currently in the proposal stages for CSS. That being said, nesting has long been a feature in many preprocessors, such as sass and less. You can also use this PostCSS plugin if you only want the nesting and nothing else.

My PostCSS Config contains postcss-preset-env already which should support for CSS nesting. I also installed postcss-nested & postcss-css-variables, just in case.

PostCSS Nested - so I can use Sass-like nesting.

A quick example that demonstrates what I've said would be the postcss nesting plugin: https://github.com/postcss/postcss-nested

When I was building a quick frontend to the LLM game, I used jQuery to quickly whip out a prototype. Only after I was happy with it, I ported the code to the modern DOM API. As a result, I totally removed the dependency on jQuery. This whole experience makes me wonder, do people still use jQuery, in this age of frontend engineering? I took some time over the weekend to port one of my old jQuery plugins. This is not intended as a how-to (we have enough of them everywhere), but rather a reflection on how things has changed over time.

Whenever the number of items increased, the browser became slow, sometimes even unresponsive. At first, we thought it was a server issue or maybe too much data. But no — the problem was hiding inside a small line of jQuery.

Ah, jQuery — the library that powered a generation of web apps.

Then we have callbacks, which were popularized by AJAX calls. Back then, with jQuery, we could define handlers to deal with both success or failure cases. For instance, let's say we want to fetch the HTML markup of this blog (skipping error failure callback for brevity), we do

One of them is JQuery created by John Resig. The library addresses extremely-frustrating issues related to cross-browser compatibility that existed at the time. To this day, it remains the most widely used JavaScript library in terms of actual page loads.

The once popular jQuery, with its strengths fully utilized in jQuery UI and Bootstrap, provides many UI components and is also friendly to backend developers, seemingly meeting the requirements. However, looking at their component implementation and resource loading forms—

This JavaScript package was intended to make HTML DOM tree traversing and manipulation easier. It is also used for animation and event handling. It has a lot of features. JQuery offers an easy-to-use API that simplifies operations like Ajax and animation. This API is compatible with a wide range of browsers. It is compatible with Chrome, Edge, Firefox, Internet Explorer, Safari, Android, and iOS.

Dive into jQuery’s impact at jQuery Documentation.

jQuery: Still relevant for quick DOM manipulations and AJAX calls (and for checking out some legacy systems)