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

@cotter45/noderjs

v1.3.0

Published

A mildly opinionated http framework for people who like Express.js but don't like the 30+ dependencies.

Downloads

1

Readme

NODER.JS

What is Noder.js?

Noder.js is what I'm calling this github repo, you can call it whatever you'd like. This is a bit of a wrapper around a basic Node.js HTTP server. It works very similarly to Express.js but is much more lightweight and ever so slightly more opinionated. There are way to many to check, but so far it's worked with every Express middleware I've tried. It's also very easy to add your own middleware in the same style that Express.js uses.

I would not recommend using this in production, it's just a fun little project I've been working on that is currently under development. Feel free to open PR's or use this project in any way that you see fit.

NPM

  • npm i @cotter45/noderjs
  • https://www.npmjs.com/package/@cotter45/noderjs

Highlights

  • Simple and easy to use
    • Works essentially the same as Express.js
    • Some notable, opinionated differences
      • This is primarily a JSON server. The strongest use case is for serving a SPA app and using the api to get data from the server.
      • Routes can only be added to Router objects, not the Server object. The Server object only has the use() method for adding middleware and useRouter() for adding routers. There is no app.get(), app.post(), etc. methods, there are only router.get(), router.post(), etc. methods.
      • Routes do not accept req, res, next as arguments. This app uses ctx: ICtx instead, which is an object containing req, res, config and whatever else you want to add to it through config.ctx when config object is passed to the server constructor.
  • Lightweight
    • 0 dependencies
  • Works with MOST Express.js middleware
    • I've tested it with a few different options, though I can't guarantee it will work with all of them
  • Easy to add your own middleware
  • FAST
    • Using wrk for testing
wrk -t4 -c300 -d30s http://localhost:8000/api
  4 threads and 300 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     9.06ms    3.29ms 107.33ms   95.77%
    Req/Sec     8.46k     0.94k    9.32k    90.58%

  1010664 requests in 30.02s, 240.96MB read
  Socket errors: connect 0, read 0, write 0, timeout 0

  Requests/sec:  33666.23
  Transfer/sec:      8.03MB
  • using autocannon with fastify's benchmark settings
autocannon -c 100 -d 40 -p 10 http://127.0.0.1:8000/api
  Running 40s test @ http://127.0.0.1:8000/api
  100 connections with 10 pipelining factor


  ┌─────────┬──────┬───────┬───────┬───────┬──────────┬─────────┬────────┐
  │ Stat    │ 2.5% │ 50%   │ 97.5% │ 99%   │ Avg      │ Stdev   │ Max    │
  ├─────────┼──────┼───────┼───────┼───────┼──────────┼─────────┼────────┤
  │ Latency │ 9 ms │ 22 ms │ 33 ms │ 51 ms │ 19.34 ms │ 7.71 ms │ 112 ms │
  └─────────┴──────┴───────┴───────┴───────┴──────────┴─────────┴────────┘
  ┌───────────┬─────────┬─────────┬─────────┬─────────┬─────────┬─────────┬─────────┐
  │ Stat      │ 1%      │ 2.5%    │ 50%     │ 97.5%   │ Avg     │ Stdev   │ Min     │
  ├───────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┤
  │ Req/Sec   │ 39039   │ 39039   │ 50719   │ 53247   │ 50415.2 │ 2371.18 │ 39035   │
  ├───────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┤
  │ Bytes/Sec │ 9.76 MB │ 9.76 MB │ 12.7 MB │ 13.3 MB │ 12.6 MB │ 592 kB  │ 9.76 MB │
  └───────────┴─────────┴─────────┴─────────┴─────────┴─────────┴─────────┴─────────┘

  Req/Bytes counts sampled once per second.
  # of samples: 40

  2018k requests in 40.02s, 504 MB read

Features

  • Basic HTTP server
    • Handles OPTIONS, HEAD, GET, POST, PUT, PATCH, DELETE
  import { Server, Router } from '@cotter45/noderjs';

  const server = new Server();
  const apiRouter = new Router('/api');

  apiRouter.get('/', (ctx: ICtx) => {
    ctx.res.status(200).json({
      message: 'Hello World'
    });
  });

  server.use(apiRouter);
  server.listen();
  • Basic routing
    • In the same style as Express.js
  apiRouter.get('/', (ctx: ICtx) => {
    ctx.res.status(200).json({
      message: 'Hello World'
    });
  });
  • Redirects
    • Works similar to Express.js, but you can only input a path or url. The status code will always be 302.
  apiRouter.get('/redirect', (ctx: ICtx) => {
    ctx.res.redirect('/api');
  });

  apiRouter.get('/redirect2', (ctx: ICtx) => {
    ctx.res.redirect('https://www.google.com');
  });
  • File serving
    • Works similar to Express.js, but these files have to have been mapped at runtime and have to be in the "static" folder. The path is relative to the "static" folder you set in the config object, default "public".
  apiRouter.get('/file', (ctx: ICtx) => {
    ctx.res.sendFile('/path/to/file');
  });
  • Download files
    • Works similar to Express.js, but these files have to have been mapped at runtime and have to be in the "static" folder. The path is relative to the "static" folder you set in the config object, default "public".
  apiRouter.get('/download', (ctx: ICtx) => {
    ctx.res.download('/path/to/file');
  });
  • Params parsed from routes
    • The normal 'gotchas' apply, but it should work as expected
  apiRouter.get('/:hello', (ctx: ICtx) => {
    return {
      message: `Hello ${ctx.req.params.hello}`
    };
  });
  • Middleware
    • Works with most Express.js middleware, though I can't guarantee it will work with all of them. Middleware takes in the req, res, next arguments.
  apiRouter.use((req: IRequest, res: IResponse, next: INextFunction) => {
    return {
      status: 418,
      message: "I'm a teapot"
    };
  });
  • Error handling
    • The framework should catch all errors and log them, but you can also add your own error handling inside the callbacks or middleware.
  apiRouter.get('/', (ctx: ICtx) => {
    try {
      throw new Error('Something went wrong');
    } catch (err) {
      ctx.logger.error(err);
      ctx.res.status(500).json({
        message: 'Something went wrong'
      });
    }
  });

  OR

  apiRouter.get('/', (ctx: ICtx) => {
    throw new Error('Something went wrong');
  });
  • Static file serving
    • This is OFF by default, turn it on with - new Server({ fileServer: true })
    • Uses 'public' dir by default but can be set to any dir inside the 'app' dir in dev, if you're using typescript or docker you will have to ensure it transfers to the correct 'dist' or 'app' dir. The file names are traversed at run time and added to a Map for quick lookup and security, so updates to the files will be reflected in the server upon a restart.
  server.staticDir('build'); // folder inside app dir
  • Basic body parsing
    • Only supports JSON so far
  apiRouter.get('/', (ctx: ICtx) => {
    ctx.res.status(200).json(ctx.req.body); 
    // returns { "hello": "world" } if body is { "hello": "world" }
  });
  • Basic query string parsing
    • Parses query strings into an object
  apiRouter.get('/', (ctx: ICtx) => {
    ctx.res.status(200).json(ctx.req.query);
    /**
     * GET /api/test?hello=world
     * returns { "hello": "world" }
     */
  });
  • Customize server level error handling
    • This is a method to customize the error handling for the server. It will catch all errors that are not handled by the router, routes, or middleware.
  server.handleError((err, req, res) => {
    res.status(500).json({
      message: err.message,
      location: 'Server Error Handler',
    });
  });
  • Customize router level error handling
    • This is a method to customize the error handling for the router. It will catch all errors that are not handled by the routes or middleware.
  apiRouter.handleError((err, req, res) => {
    res.status(500).json({
      message: err.message,
      location: 'Router Error Handler',
    });
  });

How to use

However you'd like. The infrastructure is there to use it in a similar fashion to how I would. There are a few basic example routes inside the routes/index.ts. Feel free to reach out with any questions.

There is also a dockerfile included if you prefer containerization

  • docker-compose up --build -d
  • If you're having issues with npm ci, try npm install
  • If you're having issues with static files, make sure they are getting copied into the 'app' dir of your container

TODO

  • [ ] Add more documentation / documentation site ?
  • [ ] Test with more databases
  • [ ] Test with more Express middlewares