It’s amazingly fast, cant recommend it enough.
Vite – Next Generation Front End Tooling
91–100 of 383 posts
Re: Vite – Next Generation Front End Tooling
#92how does this benchmark against doing back end development with any language and pushing vanillajs (standard javascript) to the browser? whats the big difference and why should anyone want to make this more abstract/complicated? is it trying to reduce development time?
I'd also like to know.
Re: Vite – Next Generation Front End Tooling
#93Working 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.
FOMO?
Re: Vite – Next Generation Front End Tooling
#94It 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…
Ah, the age old HN pass-time of feeling like everything needs to fit your niche, leaving a comment about how a website didn't fill in your blind spot for you rather than googling what something is with the time.
I don't think that's what OP is saying. To me, it reads like, "I'd love to know what this is, but based on the linked document and others within near proximity - I can't" which means the link requires that OP has knowledge of the frontend build world - which I will tell you is niche and disparate or that there is a big unsaid problem in this space that is non-obvious to anyone outside of it.
Curiously, both are true. Give OP some slack.
Re: Vite – Next Generation Front End Tooling
#95I'm a happy vite user, but it troubles me when I think about how complicated everything it abstracts has become. It uses rollup for some things, esbuild for others, workbox for my service worker... I switched from webpack to it, and while my config is certainly less complex, I at least could tell you what webpack is doing. Vite is magic. Can I just use esbuild yet?
I just use esbuild. If your use case is simple enough, it’s totally fine.
Re: Vite – Next Generation Front End Tooling
#96Earlier quoted context omitted.
I think Vite is waiting for code splitting and plugin support in esbuild. It does seem like magic sometimes, but the the code is relatively straightforward. It's not too complicated to dig into to the internals if you're curious about how specific configuration works under the hood. With Webpack I never really felt that way, but maybe it's some kind of subconscious bias from struggling so often with massive configs.
Code splitting issue: https://github.com/evanw/esbuild/issues/16
Hard to get a feel for if that will ever land.
Re: Vite – Next Generation Front End Tooling
#97It 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…
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 berating the maintainers I would agree with you.
tldr: "They don't get paid" is not an escape hatch for genuine, level-headed criticism, and criticism is important for FOSS to stay strong and relevant.
Re: Vite – Next Generation Front End Tooling
#98Brandon Roberts created a POC starter for Angular+Vite :
https://twitter.com/brandontroberts/status/15429548608989102...
Re: Vite – Next Generation Front End Tooling
#99Last I tested Vite (6 mo ago) it didn't support web3 lib and a few others. Has anyone tested recently?
Re: Vite – Next Generation Front End Tooling
#100I 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!
I'd recommend using ESBuild directly. The following article helped me recently to figure out how to build a browser-side library to publish to NPM, as well as bundling a Node.js server to deploy.
Build A Library With esbuild - How to bundle ESM, IIFE or CommonJS libraries with esbuild
https://medium.com/geekculture/build-a-library-with-esbuild-...
---
I had to figure out a trick for Node side to exclude external modules. In my build script:
const esbuild = require('esbuild')
const { dependencies, peerDependencies } = require('./package.json')
const external = [
...Object.keys(dependencies),
...Object.keys(peerDependencies)
]
await esbuild
.build({
entryPoints: ['src/index.ts'],
outfile: 'lib/index.mjs',
bundle: true,
sourcemap: false,
minify: false,
splitting: false,
format: 'esm',
target: ['esnext'],
external
}),