Open alinnert opened 5 years ago
To answer one of your above questions, if you don't need routing or SSR, just use Svelte on its own rather than Sapper. Sapper is, in essence, a combination of Svelte + SSR + Routing, so adding the ability to remove them would make little sense.
Can you please add a little more build features that already are part of the sapper-template? I think of things like:
static
folder (pretty much every app needs static files like icons, images, favicon, webappmanifest, ServiceWorker etc.)template.html
(e.g. to reference some of the static files - it also seems to be a little more flexible than the currentpublic/index.html
)Alternatively, can you add some documentation how to add these features? It's a little hard to figure out how the sapper-template works. Its webpack config doesn't mention the
static
folder for instance.Or does it make more sense to make the sapper-template more flexible? Or to delete not needed features manually? (For my current project I don't need a router and SSR)