Like Next.js but without SSR

[egoist]

The idea

Next.js for building single-page app (client rendering only)

I love that you can use Next.js to develop your frontend pages/*.tsx and api pages/api/*.ts at the same time in a single project, but it's also quite annoying that Next.js requires your frontend code to be SSR compatible even if you don't need any of those SSR features.

Alternatives

• Nuxt.js has a SPA mode, but doesn't support API routes.

[manniL]

Might be a good chance to contribute to the alternative then? 🤔😋

[egoist]

@manniL Yeah I opened an issue nuxt/nuxt#6862

[egoist]

What I want is actually a framework-agnostic solution, more like making Poi or Parcel support file-system based routes.

[djyde]

sounds like serlina.js.org

[egoist]

@djyde Only if it meets these requirements:

• Allow me to disable SSR so I don't have to write SSR-compatible code
• Allow me to have API pages
• Framework-agnostic front-end pages (this should be easy to implement when the framework doesn't need to worry about SSR)

[quyctd]

@egoist
Nice idea. I think Next should support disabling SSR too. But I have some questions about this idea:

• NextJS without SSR, isn't it the same as React?
• I don't get the idea behind disabling SSR and allowing API pages. I think API pages cannot work without SSR?

[egoist]

@quyctd

NextJS without SSR, isn't it the same as React?

Technically yes, but it's much more convenient than vanilla react spa, you get file-system routing for free and many other neat features.

btw in Next.js there is a way to disable SSR for certain components: https://nextjs.org/docs/advanced-features/dynamic-import#with-no-ssr so we don't need to worry about this

I don't get the idea behind disabling SSR and allowing API pages. I think API pages cannot work without SSR?

I meant the SSR for regular react pages can be disabled, you can still have a server for API pages.