With HTTP2, you can now download a bunch of smaller CSS and JavaScript files at the same time. CSS nesting is something that’s in the works and when it’s implemented, it’s going to provide native support for something that you also used to need SAS for. And again, I will link to the MDN reference for CSS variables or custom properties as they’re now called down in the show notes.
And I’ll link an article on kind of getting started with those down in the show notes.ĬSS variables let you define properties once and reuse them throughout your CSS, something that you used to need SAS for. You can create modular JavaScript files and import just the parts you need using ES modules. So today, the native web can do a lot of things that we used to have to hack around and use build tools for.
So are build tools still useful? That’s kind of what I wanna talk about today and I wanna really unpack. A lot has changed on the web in two years. So in response to those last few episodes, I actually got a note from a listener that said, what would be nice to see is alternatives to JavaScript build tools, for example, JavaScript modules and import maps.Īnd a few years back, I actually wrote an article for my newsletter over at about how build tools aren’t required to be a good developer, but how they can be nice to have. Today, I’m talking about alternatives to build tools.
#CODEKIT PROJECT VS FRAMEWORK HOW TO#
Last week, we talked about how to choose which JavaScript framework to use and how teams choose the tools they use. Hello, hello, hello, this is the vanilla JavaScript podcast. WTF is gzipping (and how is it different from minification).Build tools aren’t required to be a good developer (but they can be useful).Podcast Episode: How teams choose the tools they use.Podcast Episode: How to choose which JavaScript framework to use.In today’s episode, I talk about whether or not build tools are still useful. Download this episode’s audio file (MP3).
0 kommentar(er)
