component-template
Sapper
component-template | Sapper | |
---|---|---|
7 | 33 | |
552 | 7,187 | |
0.5% | - | |
0.0 | 5.3 | |
almost 2 years ago | almost 2 years ago | |
JavaScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
component-template
-
Should you compile components before publishing them?
Reason I'm asking is that the official component template has a build step that compiles it to pure js. But I just tried publishing it with no build step (so literally just button.svelte, index.mjs and package.json and it seems to work fine.
- Anyone have complete documentation on creating an npm package with SvelteKit?
- how do use Svelte templates with Yarn?
-
Build your own component library with Svelte
But what would it be like to build your own Svelte component library? Fortunately, there are several templates that you could start with, like the official template provided by Svelte and Svelte 3 Component Template, which are considered the go-to for building your own component library.
-
Design systems with Storybook - seeking suggestions
My question is: is there a good up-to-date Tailwind, Svelte, Storybook template out there? The one on Github is pretty old and was abandoned 5+ months ago. With the pace of change, I'm worried I'd bump into legacy bugs. I'm confused as to where to start because Svelte has an official component-template but its 10 months old. Also, which bundler is the best for a newbie? Lastly, should I use svelte-add or is there a more stable solution out there with support for Storybook?
- How to make a svelte library / a custom svelte component npm module?
-
What's the state of the art of authoring component libraries with Typescript?
The official component template still has an open issue pertaining typescript support, and there's several templates linked there. Given that time is a rare resource, and given that I frankly don't trust myself to make the right decision here up-front, I'd be interested in your thoughts and experiences. Are there trade-offs in the available TS templates? Or does one of them basically tick all the boxes already? If so, why is there no endorsed official TS template?
Sapper
- Sapper Is Now Archived
-
How I massively improved my website performance by using the right tool for the job
I built my first simple blog site in 2020 using Svelte and Sapper. The blog posts were powered by markdown files stored in the repository, and it was a great starting point.
-
SSGs through the ages: The 'Maybe Static Wasn't So Bad' era
Sapper
-
Create Beautiful Charts with Svelte and Chart js
pancake which has very scarce documentation and is in thorough experimentation(at the time of writing). Since it has been created by Rich Harris, you can rest assured that it might probably never get documentation or a stable release just like our fallen soldier sapper (a moment of silence in remembrance)
-
Svelte - JS's smallest next big thing
You might also want to check out Sapper, a framework built on Svelte that allows you to develop more advanced features like server-side rendering, offline support, and file-based routing.
-
SvelteKit & nonces
Does this help https://github.com/sveltejs/sapper/issues/343
-
Build your own component library with Svelte
SvelteKit can be considered the successor to Sapper or NextJS for Svelte. It is packed with tons of cool features, like server side rendering, routing, and code splitting.
-
How I Redesigned My Website With SvelteKit
So after using Sapper for some time, I decided to move my website to SvelteKit. I remember saying that I would not move to SvelteKit till they hit version 1 but the framework looks too promising. It had features which I needed and those features weren't in Sapper.
-
Journey to Svelte (through Gatsby)
By that time, we had some troubles with virtual dom itself in our custom rich text editor that we based on slate - it was getting a bit laggy when creating huge financial documents (they usually have enormous tables and a lot of infographics) -so we were already thinking about other options and that’s where svelte comes into the light - especially sapper which was de facto default framework to be used with svelte at that time (SvelteKit wasn’t even announced).
-
Deploying Sapper application to Deta.sh
Sapper is a framework for building web applications of all sizes, with a beautiful development experience and flexible filesystem-based routing. It is the predecessor of Sveltekit.
What are some alternatives?
svelte-adders - Easily add integrations and other functionality to Svelte apps
SvelteKit - web development, streamlined
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
vite - Next generation frontend tooling. It's fast!
svelte-materialify - A Material UI Design Component library for Svelte heavily inspired by vuetify.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
primitives - Radix Primitives is an open-source UI component library for building high-quality, accessible design systems and web apps. Maintained by @workos.
routify - Automated Svelte routes
svelte-material-ui - Svelte Material UI Components
awesome-sveltekit - Awesome examples of SvelteKit in the wild
svelte-component-template - A highly-opinionated base for building shareable Svelte 3 components
docsify - 🃏 A magical documentation site generator.