react-simplest-router
crossroad
react-simplest-router | crossroad | |
---|---|---|
1 | 5 | |
1 | 31 | |
- | - | |
10.0 | 0.0 | |
about 4 years ago | over 1 year 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.
react-simplest-router
-
Show HN: React Routing in 120 lines (including comments)
making React small libraries like these is fun.
I made one myself that was absolutely the simplest I could go for[0]
0: https://github.com/ldd/react-simplest-router
crossroad
-
What are your favorite, must-have packages when you're creating a project?
https://crossroad.page/ (1.74kb) routing, similar to React Router
-
React Router 6.4 Release
Seeing the direction React Router was taking (even before they started mixing things with data loading/management), I wrote a small alternative https://crossroad.page/ that only does routing but does it following modern React best practices:
-
Show HN: React Routing in 120 lines (including comments)
1kb is likely a lot more than what is shown here; I made a "tiny" but very complete React Router package which is very complete and minified+gzip it's just 1.8kb https://crossroad.page/
-
Not Another Framework
The author claims to "learn JS/HTML", but the first example is importing a custom component called Link with who knows what inside, which I find especially ironic because I made a small library[1] for routing in React where links are just links:
Login
[1] https://crossroad.page/
-
Ask HN: What are you using for public documentation these days?
I have an unfinished side project called Documentation Page:
https://documentation.page/
It's "unfinished" because I'd need to integrate payments and do all the accounting on my side (non-trivial as an individual living in Japan), but otherwise it's worked pretty well for my own projects.
It parses your Github Repo (according to https://documentation.page/documentation#getting-started) to generate the website. It can be a single readme.md file (for smaller projects), a folder called "documentation", or you can configure it otherwise. Some examples hosted by Documentation Page:
- statux.dev: simple single-page docs and website, menu config in https://github.com/franciscop/statux/blob/master/documentati.... Similar to form-mate.dev & vector-graph.com
- react-test.dev: split into multiple pages, you specify the folder and it'll automatically merge the markdown files. See config https://github.com/franciscop/react-test/blob/master/documen...
- crossroad.page: has an landing page, but that is not officially supported (yet). See the configs in https://github.com/franciscop/crossroad/blob/master/document...
What are some alternatives?
react-snippets - A sample of useful snippets in React
hookrouter - The flexible, and fast router for react that is entirely based on hooks
universal-router - Universal routing both for backend and frontend
page.js - Micro client-side router inspired by the Express router
manconvert - Convert troff-style man pages to doxygen source or formatted HTML
typesense-docsearch-scraper - A fork of Algolia's awesome DocSearch Scraper, customized to index data in Typesense (an open source alternative to Algolia)
one-app-router - ✨Declarative routing for One App forked from React Router 3