News for hackers. Stuff that matters.
Re:Why we switched from Webpack to Vite by nine_k on Wednesday April 28, 2021 @05:34PM (#26974510)
Most of the build tooling gets installed along the way.

The compiled JS is hundreds of bytes at most, usually because React creates a bunch of boilerplate for you (a basic CSS file, an application, a web worker, etc) which you may remove.

Re:Why we switched from Webpack to Vite by lhorie on Wednesday April 28, 2021 @07:15PM (#26975435)
Well, that's part of the jab: that you ostensibly don't need build tooling for an interpreted language, and further, that you don't even need an interpreted language in the first place considering we're talking about a platform that can do UI out of the box via a declarative language.

(Obviously, that's neither here or there when we're talking about baselines for SPAs)

Re:Why we switched from Webpack to Vite by nine_k on Thursday April 29, 2021 @01:26AM (#26977743)
ES6 is a compile target.

The actual languages are often Typescript and jsx, to say nothing of the Svelte compiler or Elm.

You can write vanilla JS without all that, of course.

Re:Why we switched from Webpack to Vite by XorNot on Wednesday April 28, 2021 @07:05PM (#26975369)
But why would you? This is the silliest way to judge something ever: what practical web application is anyone routinely building with no CSS, web workers etc.
Re:Why we switched from Webpack to Vite by Zarel on Wednesday April 28, 2021 @08:32PM (#26975999)
You would because you're comparing it to a "Hello world" command-line program in another language which also doesn't have CSS, web workers, etc.