svelte-routing
sswr
Our great sponsors
svelte-routing | sswr | |
---|---|---|
7 | 2 | |
1,972 | 225 | |
- | - | |
8.2 | 5.5 | |
8 days ago | 3 months ago | |
JavaScript | TypeScript | |
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.
svelte-routing
-
How's routing done in Vanilla Svelte?
participated in discussion about the initiative to keep svelte-routing package alive on their github issue: https://github.com/EmilTholin/svelte-routing
- UI kits, form validation, SPA routing. Why basic libraries are so hard to find.
-
Help for micro-frontend / monorepo architecture
So my questions are : Is it possible to have routes inside the MFs ? If yes, should I use something like this (https://github.com/EmilTholin/svelte-routing) even if it's not official svelte support ? I don't really see informations about entry points on the Turborepo doc. I want to be able to work on each MF independantly (I mean see them in the browser in dev mode) but then just serve them as modules for the app shell in prod mode. I imagine this is possible but is it a configuration I need to implement myself with the package.json files or is it about Turborepo ? I read this (https://michalzalecki.com/micro-frontends-module-federation-monorepo/) article about a similar approach with Webpack, but in this article I don't quite see where is the difference between the bundling part of Webpack (wich can be whatever I want Vite for Svelte, Turbo for Next, etc.) and the monorepo handling part. So how/why only one tool (webpack) instead of many others (turborepo + other bundlers) ?
-
Thoughts on Svelte
I used https://github.com/EmilTholin/svelte-routing with great success, though it looks like the maintainer has recently stopped maintaining it, and recommending sveltekit.
Still, I'd give try, it looks like people are still using it, and perhaps someone else will pick up the burden of maintenance, since there's clearly a ton of demand: https://github.com/EmilTholin/svelte-routing/issues/236
-
What's the current state of frontend frameworks/stacks thats easiest to use for small personal projects?
Second point, yes you can add routes. Here is the refence I used: https://github.com/EmilTholin/svelte-routing
-
State of the Sveltejs Ecosystem?
Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.
sswr
-
Svelte(Kit) Top 10 Wishlist for 2023
This kind of goes with #3, but would but would be cool to have more caching options for the Server and Client like SWR. It would have to support things like optimistic updates, and keep me from over fetching. Should be easy to use. https://github.com/ConsoleTVs/sswr https://react-query-v3.tanstack.com/
-
State of the Sveltejs Ecosystem?
Caching: svelte-query, sswr
What are some alternatives?
svelte-spa-router - Router for SPAs using Svelte 3
routify - Automated Svelte routes
electron-sveltekit - Electron and SvelteKit integration
svelte-query - Performant and powerful remote data synchronization for Svelte
tinro - Highly declarative, tiny, dependency free router for Svelte's web applications.
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️
svelte-apollo - Svelte integration for Apollo GraphQL