svelte-routing
svelte-query
Our great sponsors
svelte-routing | svelte-query | |
---|---|---|
7 | 15 | |
1,975 | 810 | |
- | 0.6% | |
8.2 | 2.3 | |
29 days ago | 8 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
-
Tips for sveltejs newbie
I'll use SvelteKit in the future but I wanted to learn Svelte with the most basic setup first. I don't want to use SSR anyway. I went with a Vite + Typescript setup and used this router library. It's really simple and did work without any hassle. I love the mindblowing simplicity of Svelte, the tiny builds and the blazing fast dev-server HMR. Coming from React and Vue.
-
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.
svelte-query
-
TanStack Query's Svelte adapter released!
Nice I was waiting for this! I'm using the old implementation: https://sveltequery.vercel.app/
-
When is Svelte Query coming out?
I'm aware there's another Svelte Query here but it seems like it is not maintained and will be incorporated into Tanstack Query.
-
What server-state-management / automatic-refetch library are you using with SvelteKit?
Until then I use Svelte Query
-
Some thoughts after a few months of working on Svelte projects in my spare time.
I like React Query so I would be excited to use this however it doesn't seem ready for Svelte given the docs "Coming Soon" and Svelte Query being relatively unmaintained.
-
Fetching Data in Svelte
Svelte Query :)
-
Wouldn't it be nice if {#await} blocks were compatible with RxJS Observables?
Or just use svelte-query and toss that observable junk to the side.
-
Switching from Svelte to SvelteKit
Exactly. That's the big thing I want to work on next. Not sure whether to use Svelte Query or manually cache the data. In an ideal scenario all the API calls are cached because if two users hit the site at the same time, for instance, there's no need to request the same data twice. This is getting to the edge of my skillset but psyched to try to learn this part.
-
My Favorite Tech Stack for 2022
That's it. Nothing highly sophisticated. It is mostly the tech I enjoy and I think is valuable in the future. There are also other libraries I really enjoy, like XState and React Query (there is also Svelte Query). Just to mention a few.
- Open Source contribution ideas for Svelte/SvelteKit
-
State of the Sveltejs Ecosystem?
Caching: svelte-query, sswr
What are some alternatives?
svelte-spa-router - Router for SPAs using Svelte 3
htmx - </> htmx - high power tools for HTML
routify - Automated Svelte routes
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
electron-sveltekit - Electron and SvelteKit integration
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀
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 ⚡️
sswr - 🔥 Svelte stale while revalidate (SWR) data fetching strategy