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
{{ message }}
This repository was archived by the owner on Jan 11, 2023. It is now read-only.
I want to use Sapper for its lovely file-based routing system, but don't want its SSR. I'm essentially building a SPA that will only fetch its data through AWS functions, and I want to export the app as a static site so I don't have to manage a node server.
I can write all the logic I need in [slug].svelte files without any server routes. But then running sapper export will simply eliminate them because it couldn't generate a static html file for them.
Is there a way to have a very basic setup like the one below work with sapper export the same way it would with sapper build ?
I believe there are other filesystem-based routing systems for Svelte that can be used for SPAs - but no, this isn't something that Sapper supports currently, and yes we know this is a feature lots of people want, and yes we know this is a feature that other people think is out of scope. See #383.
I want to use Sapper for its lovely file-based routing system, but don't want its SSR. I'm essentially building a SPA that will only fetch its data through AWS functions, and I want to export the app as a static site so I don't have to manage a node server.
I can write all the logic I need in
[slug].svelte
files without any server routes. But then runningsapper export
will simply eliminate them because it couldn't generate a static html file for them.Is there a way to have a very basic setup like the one below work with
sapper export
the same way it would withsapper build
?The text was updated successfully, but these errors were encountered: