Vite is excellent and https://swc.rs is another one to keep an eye on.
Vite – Next Generation Front End Tooling
161–170 of 383 posts
Re: Vite – Next Generation Front End Tooling
#162Earlier quoted context omitted.
Terrible landing page for an otherwise excellent tool. It sets up JS transpiling and bundling for you in an easy way, then provide a server with pretty fast hot reload. This solves 2 problems: - the complicated js project stack is now simple to setup, unlike with webpack - saving and seeing the result of your coding is now almost instant, unlike with CRA It's a joy to use, given that it's from VueJS author, and I hig…
One question .. Is the main goal to make development process easy or does it also have an impact on production performance as well ?
I can attest that it is a great way to spin up (and compile for server-ready HTML/CSS/JS) a React or Vue project.
Just run ‘npm init vite@latest’ and you get a basic well-organized React/Vue project ready for components and other dependencies to be dropped in.
Uses esbuild+rollup behind the scenes I believe.
If you have the luxury of picking your tools for a completely fresh web project this is a great way to do it.
Re: Vite – Next Generation Front End Tooling
#163There is no way I'm leaving webpack after those 100 years of frustration and pain. Now that I have reached an almost mediocre level of understanding of it, I am never letting it go.
Re: Vite – Next Generation Front End Tooling
#164Earlier quoted context omitted.
I can't wait for deno.js to really skyrocket. It solves all of this garbage packaging dependency nonsense.
was just reading about them, the were trending on github today.. if we want to port an existing typescript project to deno any ideas how complex it would be ?
I'd guess it would not be trivial. NPM packages are not compatible out of the box. There are workarounds, but generally speaking it's still (relatively) early days in Deno-land. Having said that, I've been playing around with the Deno Fresh framework and it's been a refreshing experience compared to typical TS based web app development.
Re: Vite – Next Generation Front End Tooling
#165Speed gains aside, it's pretty great, though I did have to provide a manual path to node_modules/some_package_here because it wouldn't serve those files in dev mode. On my computer alone. No one else. Guess I had a weird setup.
It has many years until it turns into yet another bloated "builder" if you could call it that
Overall, I continue to be impressed by whatever these guys (it's not just Ewan) do even it's getting hard to keep up at my age.
Re: Vite – Next Generation Front End Tooling
#166Earlier quoted context omitted.
This. As someone who's hung back and not switched to the hot new thing in frontend - I've learned the "old" stuff seems to mature and tends to get better. Look at React, CRA, or Redux Toolkit - they're all so much better (performant, more concise) than the original few releases now!
i dont think you find words like "deprecated" or "sunsetted" in any field as much as front end websh*t. react has changed a lot. i mean hooks pretty much is a rewrite or rethink of core concepts. nothing wrong with that per se, just that things just move to fast, there is no respect for long term stability and web seems to have a greater share of shiny new thing contrarian hipsters.
I mean, for one thing, Hooks are more than three years old at this point.
And for another, you can use React without writing a single useEffect(). Class components are still very much a thing!
Re: Vite – Next Generation Front End Tooling
#167Earlier quoted context omitted.
It's not really a correct sentence though
Isn't it? I use it and it's not clear to me what's incorrect about it.
It's too imprecise:
- People might interpret that as "drop-in replacement for webpack", which is definitely not true
- Even as just "a replacement for webpack"; Webpack and Vite have a lot of overlap, and it makes sense to compare them, but I think there are too many asterisks and nuances to say they're equivalent, in official materials, unqualified
Re: Vite – Next Generation Front End Tooling
#168It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…
Lol, I was about to comment here that I opened the docs, read a few pages, and still don't know how this works or how is it different from react for example.
No post body was provided.
Re: Vite – Next Generation Front End Tooling
#169I find it really funny that the word "javascript" doesn't appear anywhere on the entire first landing page. You have to click into "Why Vite" and then about 1/2 way into the first sentence, then you see "javascript" I was wondering "exactly what kind of front end?" C? C++? Swift? iOS front end? some kind of GUI framework? Windows app development? Modern day Javascript web ecosystem is a nightmare.
No it is not a nightmare. It is actually quite pleasant thanks to Vite.
Re: Vite – Next Generation Front End Tooling
#170I am feeling like this era of frontend javascript is too much focused on tooling and frameworks that developers spend most of their time dealing with complexities associated with them rather than focusing on creating something meaningful and useful.
Actually, you can just run 'npm init vite', choose a plain js starter, and make something 'meaningful and useful' with an awesome dev server and great bundler once you are ready to go live.