madge
svelte-routing
madge | svelte-routing | |
---|---|---|
8 | 7 | |
8,535 | 1,982 | |
- | - | |
6.3 | 8.2 | |
18 days ago | about 1 month ago | |
JavaScript | JavaScript | |
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.
madge
- Madge: Create graphs from your CommonJS, AMD or ES6 module dependencies
-
Visualisation tool
something like https://github.com/sverweij/dependency-cruiser maybe https://github.com/pahen/madge or https://github.com/antoine-coulon/skott
-
Thoughts on Svelte
You can render dependency graphs with Madge [0] (works with both TS and JS).
[0] https://github.com/pahen/madge
-
Would anyone find a visual representation of their React component tree like this be helpful?
It would be interesting to somehow overlay this graph on top of the typescript import graph (generated by something like madge). I suspect it might highlight some poorly organized regions of the codebase, because it would be obvious which component trees depend on multiple clusters of files.
- Tools to visualize the dependency graph between files of a github repo?
-
Set your project up for success
So far, I've always used a tool called madge, which saved my ass countless times.
-
ts-helper - Fast dependency cycle checker
I've also noticed that eslint cycle checking is slow for large projects, we currently use madge (https://github.com/pahen/madge) for cycle checking and its very fast and is working pretty well.
-
Is it possible to generate a flow diagram from Javascript code?
There's no VS Code extension for it AFAIK, but it's the best (and almost only) tool that I know which can do it for JavaScript code. There's also madge and emerge, in case the first one doesn't fit your needs.
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.
What are some alternatives?
vue-component-analyzer - Analyze dependency tree for Vue.js SFC (Single File Component)
svelte-spa-router - Router for SPAs using Svelte 3
eslint-plugin-import - ESLint plugin with rules that help validate proper imports.
routify - Automated Svelte routes
dependency-cruiser - Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
electron-sveltekit - Electron and SvelteKit integration
parcel - The zero configuration build tool for the web. 📦🚀
tinro - Highly declarative, tiny, dependency free router for Svelte's web applications.
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
style-resources - Style Resources for Nuxt 3
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️