svelte-routing
urql
Our great sponsors
svelte-routing | urql | |
---|---|---|
7 | 17 | |
1,980 | 8,477 | |
- | 1.2% | |
8.2 | 9.0 | |
about 1 month ago | 6 days 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.
urql
-
Top React Data Fetching Libraries
urql (8k ⭐) -> A highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
-
Apollo Layoffs
Eh, https://github.com/urql-graphql/urql is considered the improved re-architected project that doesn't contain the legacy baggage from the beginning of GraphQL like Apollo does.
-
React Real Time Messaging With GraphQL
urql docs
-
SvelteKit Server-Side Rendering (SSR) with @urql/svelte
Even though I think this solution is not too bad, I wish @urql/svelte would implement a better way to handle SSR with sveltekit. I posted a question on the urql GitHub discussions board, but I have not gotten any response yet.
- Conditionally rendering
-
End-to-end GraphQL error handling?
I want to share my approach to handling errors in GraphQL resolvers (I use GraphQL Yoga on the server-side) and pass them to the frontend side (where I use Svelte + @urql/svelte).
-
Svelte GraphQL Resources
Repository
-
Open sourcing a privacy-friendly and customizable Disqus alternate 🚀🔥
API client: urql
-
gQuery 101 – A Svelte Kit Focused GraphQL Library
big thread on it here https://github.com/FormidableLabs/urql/issues/1819
-
If every component made it's own API call to get the data, would that be an overkill for the server?
Here is link number 1 - Previous text "way"
What are some alternatives?
svelte-spa-router - Router for SPAs using Svelte 3
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]
routify - Automated Svelte routes
apollo-client - :rocket: A fully-featured, production ready caching GraphQL client for every UI framework and GraphQL server.
electron-sveltekit - Electron and SvelteKit integration
apollo - 🚀 Apollo/GraphQL integration for VueJS
tinro - Highly declarative, tiny, dependency free router for Svelte's web applications.
SWR - React Hooks for Data Fetching
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️
graphql-request - Minimal GraphQL client
sswr - 🔥 Svelte stale while revalidate (SWR) data fetching strategy
react-relay - Relay is a JavaScript framework for building data-driven React applications.