![Create React App Officially Deprecated Amid React 19 Compatibility Issues](https://cdn.sanity.io/images/cgdhsj6q/production/04fa08cf844d798abc0e1a6391c129363cc7e2ab-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Create React App Officially Deprecated Amid React 19 Compatibility Issues
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
express-routes-mapper
Advanced tools
A simple package to map your routes for your expressjs application
$ npm i -S express-routes-mapper
or
$ yarn add express-routes-mapper
After the installation you can import the package to your express project.
Create your routes file:
const routes = {
'POST /user': 'UserController.create'
};
export default routes; // module.exports = routes;
Every post request to your server to route '/user' will call the function 'create' on the 'UserController'.
Create a file named UserController.js
// es6 class syntax
export default class UserController {
create (req, res) {
res.send('created a User with es6 class syntax');
};
};
// object factory pattern
const UserController = () => {
const create = (req, res) => {
res.send('created a User with without es6 class syntax');
};
return {
create,
};
};
export default UserController; // module.exports = UserController;
Middlewares allow you perform any set of operation on a particular route. They are executed from top-to-bottom, as they are arranged in the middlewares
array.
To proceed to the next middleware or the controller, never forget to call the next()
function.
For more examples, See Middleware Example.
Middlewares can be added to a general set of routes. Such middlewares would be executed before any of the controller methods are called.
const groupedMiddleware1 = (req, res, next) => {
next();
};
const groupedMiddleware2 = (req, res, next) => {
next();
};
const router = mapRoutes(routes, 'test/fixtures/controllers/', [groupedMiddleware1, groupedMiddleware2]);
Middlewares can also be added to just a single route path.
const checkIfAutheticated = (req, res, next) => {
console.log('authenticated');
next();
};
const verifyFacebookAuth = (req, res, next) => {
console.log('unverified');
return res
.status(400)
.json({status: false, message: 'Sorry, you aren\'t authorized on facebook'});
};
const routes = {
'GET /user:id': {
path: 'UserController.get',
middlewares: [
checkIfAutheticated,
verifyFacebookAuth,
],
},
'POST /user': 'UserController.create'
};
I assume you have a folder structure like this, but it can be adapted to any folder structure.
.
+-- src
| +-- config
| | +-- routes.js
| |
| +-- controllers
| | +-- UserController.js
| |
| +-- models
| |
| app.js
|
package.json
Your app.js could look a bit like this:
The magic happens here:
import routes from './config/routes';
the file where all the routes are mappedimport mapRoutes from 'express-routes-mapper';
the package that makes the mapping possibleconst mappedRoutes = mapRoutes(routes, 'src/controllers/');
tell router to use your routesapp.use('/', mappedRoutes);
tell express to use the mapped routesimport express from 'express'; // const express = require('express');
import http from 'http'; // const http = require('http');
import mapRoutes from 'express-routes-mapper'; // const mapRoutes = require('express-routes-mapper');
import routes from './config/routes'; // const routes = require('./config/routes');
const app = express();
const server = http.Server(app);
const port = 4444;
// mapRoutes takes two arguments
// - 1. the routes
// - 2. the path to your controllers from process.cwd();
const mappedRoutes = mapRoutes(routes, 'src/controllers/');
app.use('/', mappedRoutes);
server.listen(port, () => {
console.log('There we go ♕');
console.log(`Gladly listening on http://127.0.0.1:${port}`);
});
All routes supported by the express framework is natively supported by this library (e.g. GET
, PUT
, POST
, DELETE
etc.).
const routes = {
'GET /someroute' : 'SomeController.somefunction',
'POST /someroute' : 'SomeController.somefunction',
'PUT /someroute' : 'SomeController.somefunction',
'DELETE /someroute' : 'SomeController.somefunction',
// etc.
};
Simply use a colon :
for defining dynamic routes.
const routes = {
'GET /someroute/:id' : 'SomeController.someFunction',
};
If you make a get request to http://localhost/someroute/1
the number 1
(:id) is now in the SomeController
accessible.
// object factory pattern
const SomeController = () => {
const someFunction = (req, res) => {
const id = req.params.id;
// do some fency stuff with the id
};
return {
someFunction,
};
};
export default SomeController; // module.exports = SomeController;
git checkout -b feature-name
git commit -am 'Some commit message'
git push origin feature-name
MIT © Lukas Aichbauer
FAQs
a small mapper for express routes
The npm package express-routes-mapper receives a total of 309 weekly downloads. As such, express-routes-mapper popularity was classified as not popular.
We found that express-routes-mapper demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.