You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i don't know which question it is about.
applying a sapper to this template?
or to support a template to be converted into a sapper?
well... anyway.. currently i am planning a separate
hybrid build module (ssr and csr both support)
that will make the CSR-structured SPA app be like a sapper.
CSR has many advantages. BUT Sometimes we need SSR.
I currently working on some CSR structure to create apps so that both support with SSR.
SO, Two approaches are being tried here.
One is to convert what was originally in CSR format and export static files to the entire SSR structure.
The second is to first send SSR results from Node.JS Express depending on the situation, to running as CSR by a hashbang address (In this process, if it is a general get request rather than a hashbang address, the goal is to keep responding only SSR results.)
There are searchbots of older search sites that cannot index CSR in Korea, so I am very interested in SSR. (But I also like Cordova or Electron support through CSR.)
Sappers big selling point is that its SSR and includes other things like routing. If you're going to make this template support SSR and potentially zero configuration for deploying to ziet now, I'd love that. I'm coming from a react background so I am still really new to Svelte but once I'm up to speed I'll try to contribute.
Activity
hmmhmmhm commentedon Jan 19, 2020
i don't know which question it is about.
applying a sapper to this template?
or to support a template to be converted into a sapper?
well... anyway.. currently i am planning a separate
hybrid build module (ssr and csr both support)
that will make the CSR-structured SPA app be like a sapper.
hmmhmmhm commentedon Jan 19, 2020
CSR has many advantages. BUT Sometimes we need SSR.
I currently working on some CSR structure to create apps so that both support with SSR.
SO, Two approaches are being tried here.
One is to convert what was originally in CSR format and export static files to the entire SSR structure.
The second is to first send SSR results from Node.JS Express depending on the situation, to running as CSR by a hashbang address (In this process, if it is a general get request rather than a hashbang address, the goal is to keep responding only SSR results.)
There are searchbots of older search sites that cannot index CSR in Korea, so I am very interested in SSR. (But I also like Cordova or Electron support through CSR.)
fourcolors commentedon Jan 21, 2020
Sappers big selling point is that its SSR and includes other things like routing. If you're going to make this template support SSR and potentially zero configuration for deploying to ziet now, I'd love that. I'm coming from a react background so I am still really new to Svelte but once I'm up to speed I'll try to contribute.