![]() While modern web development is awesome, there are some limitations that affect performance and user experience… Why you might still want to use build tools It’s possible to build in a modern way and never touch a build tool… but you still may want to. Gzipping is done on the server, and has a much bigger impact on JavaScript performance than minification.With HTTP/2, you can download a bunch of smaller CSS and JS files simultaneously (you used to be limited to two at a time), removing some of the benefits of concatenating everything into one file.CSS Nesting is in the works, and when its implemented, will provide native support for something else you used to need Sass for.CSS variables let you define properties once and reuse them throughout your CSS, something you used to need Sass for.You can create modular JavaScript files, and import just the parts you need using ES modules.Today, the native web can do a lot of things that we used to have to hack around and use build tools for. Are build tools still useful? Let’s dig in! Alternatives to build tools What would be nice to see on the blog is alternatives to JS build tools, for example JS modules and import maps.Ī few years ago, I wrote about how build tools aren’t required to be a good developer, but they can be nice to have.Ī lot can change on the web in two years, though. ![]() Last week, one of my newsletter readers wrote me to ask…
0 Comments
Leave a Reply. |