Live data from Hacker News

Vite – Next Generation Front End Tooling

main.vitejs.dev

111–120 of 383 posts

Re: Vite – Next Generation Front End Tooling

#111
post #60

I can’t find a vite solution for NodeJS which is disappointing. If anyone has figured out a way to ship the minimal amount of code from a NodeJS monorepo (ideally with web and server code, but generally decoupled) I’d enjoy seeing the solution!

It's possible. I often use vite with multiple build targets (decoupled but with code sharing) .. this can be specified in the rollup config options but my specific build process uses two separate vite configs to resolve some chunking challenges. Everything is parallelised for dev/build in an npm script. From memory there's a bunch of conversations relating to this kind of setup in the GitHub issues.

Edit: vite allows you to specify (e.g. node specific) exclusions/globals in the config, it also allows you to specify a 'library' build if that's what you're interested in .. with named exports, etc.

Re: Vite – Next Generation Front End Tooling

#112
post #103

Earlier quoted context omitted.

Indeed, it never occurred to me to use it with react. Vue vitesse (vite + project template) was so nice it stopped my quest.

And it’s from the guy who built Vue - maybe try that out too? You’d be surprised to get the same feeling there :-)

Not who you responded to, but trust me, I would if I could still use Vue professionally to where I could justify the time in my work and/or personal projects.

I was a huge fan of Vue 2 and Nuxt, but the work world has been heavily favoring React for a while now.

Not that everything has to be about work, but just haven’t mastered React enough to personally justify the time spent on working with Vue 3.

Re: Vite – Next Generation Front End Tooling

#113
post #97
post #75

Earlier quoted context omitted.

Quoted post unavailable.

Whether the project is FOSS or not is irrelevant. They're seeking distribution and in order to further distribute a project needs to be able to cleanly communicate why it deserves more distribution. Ironically, based on your comment, FOSS products are generally very good at this. What OP provided was criticism, and FOSS needs and welcomes criticism to stay strong and relevant. If OP was opening a GitHub issue and ber…

The argument presented was neither level-headed nor genuine.

Re: Vite – Next Generation Front End Tooling

#114

A lot of folks associate Vite with Vue or React. But the ease of use and overall dev experience in a vanilla TS/JS and web components is fantastic. IMO when paired with Vitest, the setup feels powerful, modern and lean. Would recommend.

I also feel like this is the actual use case of Vite. Don't want anything else but be able to roll a static site together, while using some vanilla html, css and js with a few assets attached.

Re: Vite – Next Generation Front End Tooling

#116
post #106

Earlier quoted context omitted.

?? 'fast' and 'fully typed APIs' do not explain anything at all. Those are completely generic descriptors. Those are arguably 'differentiators' to the problem they are solving, but they don't first explain the problem they are solving.

> they don't first explain the problem they are solving I think you're right about this and the "hero text" on their landing page should explain that in one crisp sentence. I imagine the authors of the project just aren't good at this stuff so hope they read this thread and refine the messaging.

It doesn't need to be in the 'hero text' it just needs to be somewhere.

Re: Vite – Next Generation Front End Tooling

#117
post #59

Working with front end for 5+ years have nearly made me switch careers. There's an absolute onslaught of languages, frameworks, patterns and now also "tools" that never really work in you editor, and you never really grasp before moving on to the next thing. I think me and my team have spent 90% of our time working with tooling, and all creativity and joy has gone out the window - because you never become a master, a…

> ...and you never really grasp before moving on to the next thing. Then why do you move on to the next thing? Not a frontend dev, but I notice that a lot of frontend devs seem to be really eager to jump to the next hot thing when it becomes available, even though the thing they are using is still well maintained.

Because all the upkeep happens on the new shiny toy, leaving the old ones to fester and rot away.

Heaven help you if you need to go back to a site you built for a client 4 years ago and try to make changes now. 90% chance that your build toolchain will be completely broken and fail to work.

Re: Vite – Next Generation Front End Tooling

#118

Despite all negative comments, I (and my team) switched to vite for create-react-app about two months ago, and never looked back. Builds take seconds, developer experience is amazing.a.m.a.

You may notice that all of the negative comments are around superficial nitpicking of the website copy or general bemoaning of the state of front end development. The first is sort of useful in a minor way; the second is pretty useless and generally tired. Vite is a great tool that I’d recommend for anyone who wants to speed up their front end build setup.

Re: Vite – Next Generation Front End Tooling

#119
post #59

Working with front end for 5+ years have nearly made me switch careers. There's an absolute onslaught of languages, frameworks, patterns and now also "tools" that never really work in you editor, and you never really grasp before moving on to the next thing. I think me and my team have spent 90% of our time working with tooling, and all creativity and joy has gone out the window - because you never become a master, a…

Try flutter, its a breath of fresh air!

Re: Vite – Next Generation Front End Tooling

#120
post #46

It 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…

"Next gen front end tooling" - for anyone with some vague knowledge of front end development would understand that this is going to be something like webpack, or mix, or grunt, or gulp.

Not every front page has to assume the person going to it knows nothing.

Post reply on HN