frontexpress
An Express.js-Style router for the front-end (by camelaissani)
page.js
Micro client-side router inspired by the Express router (by visionmedia)
Our great sponsors
| frontexpress | page.js | |
|---|---|---|
| - | 4 | |
| 259 | 7,662 | |
| - | 0.2% | |
| 0.0 | 0.0 | |
| over 6 years ago | 10 months ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
frontexpress
Posts with mentions or reviews of frontexpress.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning frontexpress yet.
Tracking mentions began in Dec 2020.
page.js
Posts with mentions or reviews of page.js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-13.
-
Show HN: React Routing in 120 lines (including comments)
I've used a lot of routers and my favorite is still page.js[1]. It hasn't been updated in years. But it's small, is Express-compatible (i.e. server/client routes can use the same code), and, more importantly, is hackable. I'll never use a router tied to a certain framework again (react, nextjs, etc.) because you trade flexibility for perceived convenience (e.g. using folder structure as route structure, or React component tree as route structure). But it's a terrible trade-off that paints you into a corner later, IMO. Routing can get really niche and site-dependent, so having it fully under your control is worth it.
[1] https://github.com/visionmedia/page.js
-
Dynamic routes using vanilla HTML CSS JS?
Use a simple routing library like pages.js, but in this case I feel it might be overkill.
-
[AskJS] Are there any framework agnostic routing libraries that are well supported?
I've used Page.js for a couple of SPA projects. It was last updated a couple of years ago. The documentation isn't the best, but the client-side router does its job.
-
Building a blog with Svelte: Dynamic imports For Svelte components
We're using onMount to trigger the dynamic import when this component is first rendered. My blog uses page.js as a router, so these dynamic imports are triggered by page transitions, but the logic is the same.
What are some alternatives?
When comparing frontexpress and page.js you can also consider the following projects:
director - a tiny and isomorphic URL router for JavaScript
crossroads - JavaScript Routes
pathjs - Simple, lightweight routing for web browsers
davis.js - RESTful degradable JavaScript routing using pushState
navaid - A navigation aid (aka, router) for the browser in 850 bytes~!
interfy - A Javascript library for robust web front-end routing.
SPApp - Single Page Application micro framework. Views, routes and controllers in 60 lines of code