|2 months ago||about 15 hours ago|
|MIT License||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.
Build your own component library with Svelte
10 projects | dev.to | 9 Nov 2021
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
3 projects | dev.to | 7 Oct 2021
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)
5 projects | dev.to | 22 Sep 2021
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
5 projects | dev.to | 3 Sep 2021
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.
Conheça o que são as siglas CSR, SSR e SSG
5 projects | dev.to | 27 Aug 2021
Sapper - ecossistema Svelte
I'm building a web app that aims to combine features from CodePen, Reddit, Medium, Dev.to, and Stack Overflow
3 projects | reddit.com/r/webdev | 10 Jul 2021
Lol I won’t, and to answer your question, it’s built using sapper: https://sapper.svelte.dev
Sveltekit - to use or not to use?
6 projects | reddit.com/r/sveltejs | 9 Jul 2021
I maintain a Svelte Starter Kit and all I had to do between several updates is change the layout file names, simplify the hooks, and convert the config file extensions. If you're learning Svelte in 2021, you shouldn't miss learning it, as it's "the missing CLI" and the svelte team's favoured project structure, to build full-stack server rendered and static sites, with File/Folder based routing, focus on server-less with adapters, API routes, and good baked-in conventions and constructs to support common web app needs. It's a successor to Sapper which served the aforementioned needs, with exception of adapters, which is special/unique(with no officially provided parallels in Next.js/Nuxt ecosystems yet) way to make vendor-agnostic, server-less first deployment concern a seamlessly integrated part of the framework.
1 project | dev.to | 28 May 2021
Since Node v12, ES modules has been enabled by default. Hence my use of '.mjs' to run my file including a node module. Another way to resolve this issue is to use import with Node.js, you have to edit the package.json to 'type':'module'. However, using this caused my Sapper server to crash since it wasn't supported, as the rollup file outputs the format to commonjs Explained in (this GitHub issue).
planning to learn svelte for front-end, need advice
6 projects | reddit.com/r/sveltejs | 23 May 2021
I am not sure whether or not they help you, but both svelte.dev and sapper.svelte.dev are open source. both of those projects are built on sapper, not svelte-kit, but a quick look at kit.svelte.dev/migrating should be enough to see what changed. (both of those make heavy use of markdown files so I don't know how helpful they are, also if you need help translating something from sapper to svelte-kit just reply and I'll probably be able to help)
Difference between SSR, SSG, CSR and SPA
10 projects | reddit.com/r/nextjs | 11 Apr 2021
SSR (Server Side Rendering): the process of receiving a request from the client, e.g: a user goes to https://example.com to load the homepage, and returning a rendered version of the webpage with all the needed info and data to load it as fast as possible. Examples of this are [NextJS](https://nextjs.org), [NuxtJS](https://nuxtjs.org/), [Angular Universal](https://angular.io/guide/universal), [SvelteKit](https://kit.svelte.dev/) (currently in Beta) and [Sapper](https://sapper.svelte.dev/) (currently going deprecated);
Meet our new pei.
1 project | reddit.com/r/sharpei | 4 Dec 2021
Her name is Svelte (slender and elegant). But the name was inspired from a software framework called Svelte
Svelte's lifecycle methods can be used anywhere
3 projects | dev.to | 30 Nov 2021
I haven't quite wrapped my mind around it, but you can even use afterUpdate in Svelte to replicate React's useEffect hook. See this example from Rich Harris, which I found in an interesting GitHub issue discussing the edges of Svelte's reactivity.
Top 6 Frontend Frameworks in 2022 for Web Development
2 projects | dev.to | 29 Nov 2021
How to update values in database shown in html table?
3 projects | reddit.com/r/cs50 | 24 Nov 2021
This is a bit complex, and you might want to use a UI framework like React, Vue, or Svelte.
I built svelte-link-preview
2 projects | reddit.com/r/sveltejs | 23 Nov 2021
When linking https://svelte.dev/ the description is set to null which is probably due to the uppercase letter in the meta tag? Is this something the proxy could/should take into account so the description is read nevertheless?
The Sacred Steps to Achieving Good Documentation
5 projects | dev.to | 23 Nov 2021
Of course, the correct tool, as usual, depends on the requirements of your project. For an API, Apiary might be your best choice, if you want a more generalized documentation you Read the Docs might give you a quick and free way to have your documentation up and running, however if you really want a lot more control over styling and such, docussaurus can really help. There is also a last option which is quite rare though: just make a static website from the ground up. You can use React, Svelte, or really anything you want to build a documentation site. It's a lot more work than any of the previous options, but if you truly believe you need to control every single aspect of your documentation it is still a possibility.
Adding React to an Optimizely UI - Part 2
7 projects | dev.to | 19 Nov 2021
But the big name players are still React, Angular and Vue, in my opinion (and I fully confess there was a lot of my opinion in the decision phase here!). Other noteworthy candidates were Next.JS and Svelte.
Dev in Dev: Issue 1 Nov 2021
3 projects | dev.to | 18 Nov 2021
AJAX and Single Page Apps ushered in a new age of web experiences, however it is not without it's flaws. Transitional Apps is a new paradigm of web apps which proposes a new direction. Rich Harris of Svelte introduces this concept at Jam Stack Conf 2021.
Testing Svelte components with Jest and Vite
8 projects | dev.to | 18 Nov 2021
6 projects | reddit.com/r/u_liaguris | 17 Nov 2021
What are some alternatives?
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.
awesome-blazor - Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
Next.js - The React Framework
SvelteKit - The fastest way to build Svelte apps
Aurelia 1 - The Aurelia 1 framework entry point, bringing together all the required sub-modules of Aurelia.
Angular - The modern web developer’s platform
Gatsby - Build blazing fast, modern apps and websites with React
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.