npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

express-lazy-router

v1.0.6

Published

Lazy loading for express router

Downloads

20,319

Readme

express-lazy-router

Lazy loading for express router.

Motivation

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

Install with npm:

npm install express-lazy-router

Usage

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`)
});

Options

preload

Default: false

If it is true, preload the router module as soon as. It does not mean sync loading.

Examples

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
  • complete to launch the express app
  • GET /api/status
  • load api.js
    • Compile api.js by babel or ts-node
  • { ok: true }

Limitation

Avoid to use non-path router

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}`)
});

Changelog

See Releases page.

Running tests

Install devDependencies and Run npm test:

npm test

Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, please create an issue.

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Author

License

MIT © azu