[Question] Does SSR with Vue really need a build? (i.e. Handle component files like Ts-Node)

[arpowers]

Since SSR is essentially just rendering a "snapshot" of the initial state of the HTML generated by components, shouldn't it be possible to handle component files in a similar way to how ts-node deals with .ts files?

Essentially we could use require.extensions to convert .vue files to es modules, add a .ts extension and then handle them with ts-node... giving us the ability to use Vue components without the hassle of a build.

I know, for some reason, Node says not to use this but it's a critically useful feature when implemented carefully (as with ts-node)

[underfin]

Essentially we could use require.extensions to convert .vue files to es modules, add a .ts extension and then handle them with ts-node... giving us the ability to use Vue components without the hassle of a build.

That can be do. But most case we need fast performannce at runtime, vue template always need tranformed (this is what build is going to do).If you not transform it at build, you must do it at runtime.

[arpowers]

@underfin its not a performance issue, as in TsNode, the compiled code is cached after the first run.

[underfin]

Yeah. That always need tranformed at runtime whaterever cached or not cached.

[arpowers]

@underfin In a way different than ts-node? If so, why?

[underfin]

If you want to run it by the similar way of ts-node, it can should work for you. But for most users, them need build for ssr for now.

This question same as why we need build with component for browser runtime.The performance actually is important for node server and client.

[arpowers]

What I'm trying to say is that ts-node is quite performant, and Vue/Vite could work the same way.

This is accomplished because the FIRST time any .ts file is run, it is transpiled and that transpiled version is cached via require.cache....

I believe that we could do the same with vue files. Transpile them and cache that result.

The advantages being:

• Real time development with SSR and no builds
• Simplification of SSR (no build logistics)

Can we keep this open as a suggestion please? I believe it needs more feedback. @underfin

[underfin]

Real time development with SSR and no builds

This is a nice point, it can be faster with ssr hmr .But I also think need build for production. I reopen this hope get other people give opion.

[frandiox]

@arpowers Very interesting idea. It could be useful at least for development in order to have a local SSR environment that doesn't require build watching, like what you mentioned in another issue.

In production, however, I think a build would still be better at least for short-lived environments such as serverless functions or workers. Maybe it could be fine for Node servers 🤔

[yyx990803]

Closing for #1290