madge VS tanstack.com

something like https://github.com/sverweij/dependency-cruiser maybe https://github.com/pahen/madge or https://github.com/antoine-coulon/skott

You can render dependency graphs with Madge [0] (works with both TS and JS).

[0] https://github.com/pahen/madge

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.

So far, I've always used a tool called madge, which saved my ass countless times.

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.

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.

- UI kit (I personally have good experience with React Material UI - https://mui.com/; there is also https://tanstack.com/)

I recently listened to a talk by Tanner Linsley, the creator of TanStack (React Query), about his personal experience in the open-source community. I highly recommend listening to it:

Link - https://tanstack.com/

tanstack router

Svelte doesn't use a virtual DOM and when it compiles, it only targets what you are specifically using it for.

The thing with Svelte is that for a big project (like an SPA) you're going to end up using SvelteKit, because that's where all the development focus is for things like routing etc... and SvelteKit isn't nearly as settled. As in, there aren't developed "patterns" for doing a lot of things yet so it's a lot of trailblazing. There's also some features that are missing and on the roadmap but SvelteKit just hit 1.0 in December (these are usually more obscure things but you will still likely encounter them if you're building something of moderate complexity.)

I still think overall it would be fine to use for a big project, but a year from now I think it will be a much easier choice. Something that is happening right now is a lot of big players in the wider JS ecosystem are transforming from being React specific to framework agnostic:

- NextJS -> Auth.js: https://twitter.com/balazsorban44/status/1603082914362986496

- React Table / React Query -> TanStack Table, TanStack Query: https://tanstack.com/

This has all happened in the last few months. So it's still new, and they're still improving as they move away from being React specific. People rely on those projects. As more move in that direction I think it will become easier and easier.

5: TanStack React

This is where the TanStack comes in. I really hope that the fact that the TanStack has all packages built in a framework-agnostic way will help adoption of non-React libraries over time. Think about it: If you need to fetch some data, render a table and maybe virtualize it - you can do all of that with the TanStack. And if you know how to do this in React, you also already know how to do it in Solid, Svelte or Vue.

Other popular packages in this generation include the tanstack series of packages:

Disclaimer, I'm the founder of AG Grid, however I'm also friends with Tanner. You can see from tanstack.com that AG Grid is both a sponsor but more importantly a partner with TanStack.