Trying out a router for Ripple.

[emeraldlinks]

Hello Ripple community 👋,

I’m really excited about this framework and would love to contribute. A few days ago, I asked about a router, and since it’s not yet a built-in feature, I created a basic router for testing.

So far:

It supports dynamic routes like /users/:id.

Navigation works without page reload in most cases.

Current limitation:

I couldn’t fully get the router to render pages based on the path without a full page reload in all scenarios.
Here’s the repo I’ve been working with:
https://github.com/emeraldlinks/rippleapp
http://localhost:3000/
http://localhost:3000/about
http://localhost:3000/users/42

[WebEferen]

Hi @emeraldlinks

Feel free to use this router I've created: https://github.com/WebEferen/ripplejs-router
Mind that it might be changed over time. There will be an addition that will support SPA like sites without redirect (or navigation based routing).

[emeraldlinks]

Hi @WebEferen

Thank you for this. But i cant seem to get it to work.

[WebEferen]

Ohh I'm in the middle of transition into ripple-router package.

For now, use ripplejs-router (install it and you should be able to use it following the README

[emeraldlinks]

So I finished the routing system I was working on Ripplejs. It’s a comprehensive all in one router that covers almost every need of the user. It’s file based, zero config needed which can still be configured to taste if the defaults are not enough. It works exactly like NextJS and NuxtJs routing system with all the browser navigation apis. Easily extract pathnames, query parameters, loading state, etc. also it comes with a zustand equivalent global state system that’s accessible both in and out of components. The state system has both read, delete and update with option for persistent storage with keys. Everything is up to date with the Ripplejs recent changes on reactivity.

I intend to publish this by this weekend.