Testing JavaScript without a (third-party) framework – alexwlchan https://alexwlchan.net/2023/testing-javascript-without-a-framework/ -
@edsu no-build JS setups. So hot right now.
Mozilla figured out how to put JS to serious use before `npm install`* was ever a thing. Of the hundreds of thousands of lines of JS powering Firefox (at least up until I called it quits on my hope that Mozilla would stay out of the gutter ~10 years ago)—mostly just a bunch of script elements and pre-ES6 JSM `import` statements. Very little "build" work in sight.
* or NodeJS or even Firefox, for that matter
@edsu I was very pleased when a few years ago I looked at the implementation of the WebKit Inspector (which is on GitHub nowadays) and saw it was basically the same thing: <https://github.com/apple-oss-distributions/WebInspectorUI/blob/4e0b016d7ece3a68a7a1c67764dcc9bf8cd8d6b6/UserInterface/Main.html>
To anyone and no one in particular: you now have permission to respond with "STFU" to any insolent jabberwocky insisting that you have to follow what the NodeJS/NPM community deems to be "best practice".
The story of JS's history for programming in the large (let's call it "industrial use") is so much fuller (and smarter) than the things NPMers have convinced themselves is essential for taming what they treat as irreducible complexity.
Around the time that I wrote "How to displace JS" <https://www.colbyrussell.com/2019/03/06/how-to-displace-javascript.html>, I checked the then-latest README for instructions about doing a hello-world program using create-react-app. It was fuckin' 500 fuckin' megabytes *just* to be able to do a successful `npx create-react-app` and `npm start` and show the word "hello". Nuts!