svelte-routing
dioxus
svelte-routing | dioxus | |
---|---|---|
7 | 155 | |
1,989 | 18,688 | |
- | 12.2% | |
7.9 | 9.9 | |
17 days ago | 1 day ago | |
JavaScript | Rust | |
MIT License | Apache License 2.0 |
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.
dioxus
-
Dioxus 0.5: Web, Desktop, Mobile Apps in Rust
We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...
Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys
- Container2wasm: Convert Containers to WASM Blobs
-
Why Are Tech Reporters Sleeping on the Biggest App Store Story?
I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.
-
Using Dioxus with Rust to build performant single-page apps
While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.
-
Package All the Things
You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).
- Show HN: Play Euchre with AI Bots
- Dioxus: Fullstack GUI library for desktop, web, mobile, and more
- Projects to contribute to?
- Ask HN: React Native or Flutter for a new app in 2023?
-
Announcing Floneum (A open source graph editor for local AI workflows written in rust)
Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI
What are some alternatives?
svelte-spa-router - Router for SPAs using Svelte 3
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
routify - Automated Svelte routes
yew - Rust / Wasm framework for creating reliable and efficient web applications
electron-sveltekit - Electron and SvelteKit integration
leptos - Build fast web applications with Rust.
tinro - Highly declarative, tiny, dependency free router for Svelte's web applications.
sycamore - A library for creating reactive web apps in Rust and WebAssembly
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
iced - A cross-platform GUI library for Rust, inspired by Elm
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond