7 ms·

Open alternative to Next.js: https://vite-plugin-ssr.com/ https://vite-plugin-ssr.com/ (I'm its author). Open: - Choose any UI framework you want (React/Vue/S

Open alternative to Next.js: https://vite-plugin-ssr.com/ https://vite-plugin-ssr.com/ (I'm its author). Open: - Choose any UI framework you want (React/Vue/Solid/...) - A lot more flexible than Next.js (e.g. i18n and base assets configuration are fundamentally more flexible) - Keep architectural control (vite-plugin-ssr is more like a library and doesn't put itself in the middle of your stack) - Use your favorite tools. And manually integrate them with vite-plugin-ssr (for full control without surprises). - Deploy anywhere (and easily integrate with your existing server/deploy strategy) - Open roadmap - Ecosystem friendly The upcoming "V1 Design" has been meticulously designed to be simple yet powerful. Once nested layouts, single route files, and typesafe links are implemented vite-plugin-ssr will be pretty much feature complete. Note that, with vite-plugin-ssr, you implement your own renderer, which may or may not be something you want/need/like to do. Built-in renderers are coming and you’ll then get a zero-config DX like Next.js (minus extras like image processing as we believe they should be separate libraries). Web dev isn't a zero sum game - a vibrant and healthy ecosystem of competing tools can co-exist. (I'm close to be able to make a living with sponsors.) Vision is to make a truly open and collaborative foundation for meta frameworks. Let me know if you have any questions.

iamsaitam 3y ago
Even though you go on explaining what you mean by "open", seeing that the common definition is "open (source)", I'd go for a different qualifier.
- 3np 3y ago
  It's available under MIT License hosted on GitHub. Am I missing something? https://github.com/brillout/vite-plugin-ssr/blob/main/LICENSE.md https://github.com/brillout/vite-plugin-ssr/blob/main/LICENS...
  - brillout 3y ago
    I think parent means that both Next.js and vite-plugin-ssr are open source, so "open(-source)" isn't a differentiator. I agree although we think we can keep the word "open" and make it clear that we're takling about being a "open framework" (and not only open source).
- brillout 3y ago
  Yea, we've plans to improve communicating that. (Although we do plan to stick to the word "open".)
eric-burel 3y ago
Next.js pseudo-alternatives are usually subpar, because they misunderstand Next.js approach and implement a very simplified vision of it (eg they can't even tell the difference between client-side rendered SPA and HTML export). This one doesn't seem to fall in this trap, from the documentation it seems a very well thought library. Great work!

iamsaitam 3y ago

Even though you go on explaining what you mean by "open", seeing that the common definition is "open (source)", I'd go for a different qualifier.

3np 3y ago
It's available under MIT License hosted on GitHub. Am I missing something? https://github.com/brillout/vite-plugin-ssr/blob/main/LICENSE.md https://github.com/brillout/vite-plugin-ssr/blob/main/LICENS...
- brillout 3y ago
  I think parent means that both Next.js and vite-plugin-ssr are open source, so "open(-source)" isn't a differentiator. I agree although we think we can keep the word "open" and make it clear that we're takling about being a "open framework" (and not only open source).
brillout 3y ago
Yea, we've plans to improve communicating that. (Although we do plan to stick to the word "open".)

eric-burel 3y ago

Next.js pseudo-alternatives are usually subpar, because they misunderstand Next.js approach and implement a very simplified vision of it (eg they can't even tell the difference between client-side rendered SPA and HTML export). This one doesn't seem to fall in this trap, from the documentation it seems a very well thought library. Great work!