3 ms·
>Understanding webpack, and why it’s important Not sure how Webpack is being attributed as being a part of Javascript here. It's a bundler, with Javascript sup
by DigitalSea 7y ago
>Understanding webpack, and why it’s important
Not sure how Webpack is being attributed as being a part of Javascript here. It's a bundler, with Javascript support being one small piece in a much larger puzzle. It's not even the only bundler out there, JSPM is currently in beta which goes in a different direction than Webpack, then you have Parcel and other options as well.
>Understanding babel, and why it’s important
Eh. I haven't used Babel in years since switching to TypeScript.
This doesn't seem very focused on Javascript, seems like a lot of emphasis being placed on tooling more than the language itself.
- IggleSniggle 7y agoI agree with your assessment, but the “major” web framework ecosystem (React, Angular, Vue) all use webpack as a de facto part of their toolchain. And webpack, in turn, relies on babel. Other bundlers are commonly used as part of plugin system. Regardless of transpiler tooling, the tooling is how most people are confident in using the most modern variants of JavaScript code. So it’s an important part of the modern js story.
- davnicwil 7y agoI agree, JavaScript the Good Parts was written in a time when there essentially was no ecosystem in Javascript to speak of, so it was by definition focused on nothing but the language. In 2019 JavaScript comes as part of a much more developed (and useful!) ecosystem that is completely tied in with tools such as Babel and Webpack and the alternatives mentioned. Even if you don't use or want to use any particular one of them, knowledge of all of them, at least what they do, is more or less essential to work in modern JavaScript to understand how the ecosystem fits together and how most projects out there use the language.