# Why I Chose SapperJS For My Website, And What I've Learned About The Framework So Far

DevFeed: [Why I Chose SapperJS For My Website, And What I've Learned About The Framework So Far](<https://devfeed.tech/articles/why-i-chose-sapperjs-for-my-website-and-what-i-ve-learned-about-the-framework-so-far-35057.md>)

Original publisher: [Read original article](<https://markushatvan.com/blog/why-i-chose-sapperjs-for-my-website-and-what-ive-learned-about-the-framework-so-far/>)

Published: 2020-06-13T00:00:00Z

Content type: opinion

Language: en

Sources: [Markus Hatvan](<https://devfeed.tech/sources/markus-hatvan.md>)

Topics: [Framework](<https://devfeed.tech/topics/framework.md>), [Jamstack](<https://devfeed.tech/topics/jamstack.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [framework](<https://devfeed.tech/tags/framework.md>), [jamstack](<https://devfeed.tech/tags/jamstack.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [website](<https://devfeed.tech/tags/website.md>)

## AI overview

A developer explains why they chose SapperJS for a website built with a modern JAMStack setup. They compare alternatives including Next.js, Gatsby, Hugo, and Nuxt.js, considering performance, SEO, developer experience, innovation, and the opportunity to explore different JavaScript frameworks.

## Source excerpt

Since I wanted to go for a website built on a modern JAMStack setup, I had these options based on framework popularity and matureness.