Lazy loading for express router.
I've used ts-node(ts-node-dev) for developing Node.js Web Application. It means that compile all TypeScript files at start time.
Many compilation make startup of the web app slow. Lazy routing avoid this compilation overhead by compiled when needed.
In a frontend, We have already used lazy loading with router like React Router, Vue Router.
Also, webpack support experiments.lazyCompilation as experimentally.
My motivation that We can do lazy routing in Node.js Express routing too.
Results of my project:
Use ts-node-dev + express
- Before:
- 123 ts file Compilation
- Total startup time: 34236ms
- After(use express-lazy-router):
- 14 ts file Compilation
- Total startup time: 14238ms
- Summary:
- Compilation time is 200ms per 1 ts file
Install with npm:
npm install express-lazy-router
import express from 'express';
import { createLazyRouter } from 'express-lazy-router';
const lazyLoad = createLazyRouter({
// In production, Load router asap
preload: process.env.NODE_ENV === 'production',
});
const app = express();
// Load ./path_to_router.js when receive request to "/path_to_router"
app.use(
'/path_to_router',
lazyLoad(() => import('./path_to_router')),
);
app.listen(8000, () => {
console.log(`Example app listening at http://localhost:8000`)
});
Default: false
If it is true
, preload the router module as soon as.
It does not mean sync loading.
Before: No lazy loading
index.js
:
import express from 'express';
import api from "./api";
const app = express();
app.use(
'/api',
api
);
app.listen(8000, () => {
console.log(`Example app listening at http://localhost:8000`)
});
api.js
:
import express from 'express';
const router = express.Router();
// GET api/status
router.get("/status", (_, res) => {
res.json({ ok: true })
});
export default router;
Behavior:
- load
index.js
- load
api.js
- complete to launch the express app
GET /api/status
-
{ ok: true }
After: lazy loading for api.js
index.js
:
import express from 'express';
- import api from "./api";
+ import { createLazyRouter } from 'express-lazy-router';
+ const lazyLoad = createLazyRouter({
+ preload: process.env.NODE_ENV === 'production',
+ });
const app = express();
app.use(
'/api',
- api
+ lazyLoad(() => import("./api"))
);
app.listen(8000, () => {
console.log(`Example app listening at http://localhost:8000`)
});
api.js
: No need to change!
Behavior:
- load
index.js
- complete to launch the express app
GET /api/status
- load
api.js
-
{ ok: true }
The more details behavior when you use loader like @babel/register or ts-node.
- load
index.js
- Compile
index.js
by babel or ts-node
- Compile
- complete to launch the express app
GET /api/status
- load
api.js
- Compile
api.js
by babel or ts-node
- Compile
-
{ ok: true }
NG: express-lazy-router does not expect this way.
import { createLazyRouter } from 'express-lazy-router';
const lazyLoad = createLazyRouter();
const app = express();
app.use(lazyLoad(() => import('./path_to_router')));
app.listen(port, () => {
console.log(`Example app listening at http://localhost:${port}`)
});
See Releases page.
Install devDependencies and Run npm test
:
npm test
Pull requests and stars are always welcome.
For bugs and feature requests, please create an issue.
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature
- Commit your changes:
git commit -am 'Add some feature'
- Push to the branch:
git push origin my-new-feature
- Submit a pull request :D
MIT © azu