What is missing in Sapper when compared to Gatsbyjs for JAM stack?

[kaushalyap]

I hope someone create a checklist of what is missing in Sapper when compared Gatsbyjs for JAM stack in order to keep track of Sappers progress.

[andriijas]

I agree. Something like gatsby (react) or Gridsome (vue) for svelte would make it really interesting. I like the idea of hooking up data with plugins (or building my own), a graphql layer, generate static html and adding dynamic content on top where needed. And if that dynamic part is precompiled without any runtime library. Well then Im in cloud heaven 😂

[antony]

It sounds like the two of you are best placed to give an idea of what is missing! It could certainly be a good base for a roadmap of sorts for Sapper.

[kaushalyap]

@andriijas Can you please create a checklist? I could fill in if something is missing.

[swyxio]

just linking my project here https://github.com/sw-yx/ssg as well as https://github.com/sveltejs/sapper/pulls/nealalpert

[andriijas]

• Pre-rendered HTML
• Automatic Code Splitting
• Follows PRPL-pattern
• Smart link prefetching
• Progressive Images
• Plugin architecture
• "Bring your own data"
• Graphql layer

[bummzack]

Merging #869 would be a great first step. It would turn a broken system into a working one.
This issue alone is stopping us from considering svelte/sapper for any future projects at the moment.

[kaushalyap]

In addition to what @andriijas mentioned

• PWA support
• Authentication ex: authentication in gatsbyjs
• Security baked in, avoiding things like Gatsby Content Security Policy (CSP) gatsbyjs/gatsby#10890
• Themes ex: gatsbyjs themes
• Incremental builds

Related issues from the repo

• Hook to generate 404 pages for sapper export : Hook to generate 404 pages for sapper export #557
• Static site optimizations: Static site optimisations #172
• Better prefetch cache? Better prefetch cache? #483
• Prioritise prefetching: Prioritise prefetching #59
• Preload all Route assets: Preload all Route assets #70
• PWA Install prompt not showing anymore: PWA Install prompt not showing anymore #754
• Image Processing Brainstorm: Image Processing Brainstorm #897
• Feature Request: Automatic Build Time Static Optimization: Feature Request: Automatic Build Time Static Optimization #1046
• Inline main.js: Inline main.js #12
• Sapper export: when copying static files, also set a(ccess)time and m(odification)time for the files : Sapper export: when copying static files, also set a(ccess)time and m(odification)time for the files #1110

For image optimization there is svelte-image by @sw-yx

---

Updates:

• Added Sapper export: when copying static files, also set a(ccess)time and m(odification)time for the files #1110 mentioned by @sw-yx
• Checked out Sapper export: when copying static files, also set a(ccess)time and m(odification)time for the files #1110

[swyxio]

i know both well. i'd say a subset of gatsby plugins can be adapted with low pain to work with sapper. the rest are unfortunately too React specific. would need adapters, or a "react mode".

[swyxio]

linking #1110 - when copying static files, also set a(ccess)time and m(odification)time for the files

[arxpoetica]

@andriijas Sapper does automatic code splitting and link prefetch

[janat08]

Routify is alternative to sapper.

[kaushalyap]

Does team any plans related to this? I hope they prioritize this.

[antony]

@kaushalyap it's certainly on our RoadMap, but as with anything, we will always welcome somebody from the community to spearhead and push this forward.

[ghost]

Another suggestion that applies to sapper in general but especially for static sites which are built for speed:

• Minification of ALL html (ssr html literals etc. which can still be found unminified in the exported output)

[floer32]

[ side note ... @sw-yx could you edit your comment since the project is defunct? I will say: thank you, though! I learned about elderjs via your comment, and i'm going to try that for another project (while still using sapper in another case) ]