solid-router VS solid-transition-group

Solid Router - https://github.com/solidjs/solid-router

Fastify DX follows the same routing principles as Next.js and Remix. The first page is /pages/index.{js|ts} and other pages can be linked to by using solid-app-router. Dashboard would link to /pages/dashboard.{js|ts} and SolidJS Article would link to /pages/articles/[id].{js|ts}. SSR, Streaming etc. can be fine-tuned by exporting variables in the page. Check out the examples for streaming, SSR, etc. in the fastify dx starter kit

Hello, I've recently created a single page web app with multiple routes. I'm using vercel for hosting and solid app router (https://github.com/solidjs/solid-app-router) for the router bit. When I go to my page on vercel and click on a link, for example, /help then reload the page it leads to 404 not found. If I go straight to that link it has the same error. In my dev environment it functions as I'd expect. After reloading it loads the help page. Is there a way to configure vercel to behave correctly?

Agree wrt. Solid being easier to reason about.

Is the router you are using solid-app-router [1] ? Have been working with it for last few months and it has been generally stable (my usecases are not particularly complex though).

The docs for the solidjs core has also massively improved recently.

[1] https://github.com/solidjs/solid-app-router

With regards to third-party libraries, Solid does not have a lot yet, but it does have first-party libraries. Its first-party libraries are the equivalent of other popular libraries in other JavaScript libraries, such as Solid App Router for routing, Solid Testing Library for writing component tests, and Solid Transition Group for animations.

Since official SolidJS starter template are vite-based we can easily use vite-plugin-pages to create automatic routing a.k.a file based routing with official solid-app-router package.

Hmm.. Remix is based around their router. And a nested router is what we need to for Solid (see Solid App Router https://github.com/solidjs/solid-app-router). I think the challenge is that we don't render like React. Not at all. I've found most cases where that assumption exists to be incompatible.

That being said the work has already started on a starter with Nested Routing/Automatic File Based Routing + Code Splitting/Parallelized Data Fetching/Streaming SSR/Multiple deployment adapters. We're given it the same focus on performance that we've given the rest of Solid.

Here is the recent Vercel Edge Function demo we made with it: https://twitter.com/RyanCarniato/status/1453283158149980161

Solid has an impressive collection of first-party tools developed by its creator - Ryan Carniato - and other contributors. There you’ll find Solid equivalents of some popular libraries from other ecosystems, like Solid Transition Group, Solid Refresh (for Hot Module Reloading - HMR), Solid App Router, and more!

I'd argue SolidJS ecosystem is ready. For UI kits, there's Kobalte, SUID, Bootstrap, for forms there's Felte and Modular Forms, for animations there's Motion One and Solid Transition Group, for tables there's AG-Grid and TanStack Table, for hooks/utilities/Browser API wrappers there's Solid Primitives. You can also easily use existing vanilla js packages because SolidJS doesn't rerender.

With regards to third-party libraries, Solid does not have a lot yet, but it does have first-party libraries. Its first-party libraries are the equivalent of other popular libraries in other JavaScript libraries, such as Solid App Router for routing, Solid Testing Library for writing component tests, and Solid Transition Group for animations.

Solid has an impressive collection of first-party tools developed by its creator - Ryan Carniato - and other contributors. There you’ll find Solid equivalents of some popular libraries from other ecosystems, like Solid Transition Group, Solid Refresh (for Hot Module Reloading - HMR), Solid App Router, and more!