3 ms·
Congrats on launching! I don't quite understand what this solves relative to vite. One sentence on that in the README would probably go a long way.
by rgbrgb 3y ago
Congrats on launching! I don't quite understand what this solves relative to vite. One sentence on that in the README would probably go a long way.
- l5870uoo9y 3y agoWas hoping for a second it was a challenger to the the NextJS front-end monopoly. As I understand it enables you to start Vite development without setting up a server/TS while keeping it lightweight.
- madeofpalk 3y ago> NextJS front-end monopoly What? I guess NextJS has a monopoly for a extremely specific type of website and developer, but this statement is really doesn't make sense.
- dcre 3y agoTry Remix! https://remix.run/ https://remix.run/
- antifa 3y agohttps://nuxt.com/ https://nuxt.com/
- ericyd 3y agoThe blog post mentions that using vite requires installing a dev env via npm, and that wasn't straightforward enough for the authors use case. I still don't understand though, because vlite is also installed via npm, as would react et. al. How is vlite easier? One less (very small) config file?
- _kst_ 3y agoIn addition to a sentence about what this solves relative to Vite, another sentence saying what Vite is would also be helpful to those of us who have never heard of Vite. A link to https://vitejs.dev/ https://vitejs.dev/ would probably suffice, though even that site doesn't seem to explain much until you follow some links. I'm very probably not the target audience for this, but the README should have enough information to tell me I'm not the target audience. (From that site: "Vite (French word for "quick", pronounced /vit/, like "veet") is a build tool that aims to provide a faster and leaner development experience for modern web projects.")