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

@globality/nodule-express

v0.6.0-dev766

Published

Node Express Conventions

Downloads

86

Readme

@globality/nodule-express

Node Express Conventions

nodule-express aims to define basic routes for Node Express gateways to focus on definiing logic for actual API endpoints and leave basic error handling and express set up to this library

Bindings

By importing nodule-express, the following bindings are made available.

Middleware

  • middleware.basicAuth injects a basic auth middleware
  • middleware.errorHandler injects a middleware to show unhandled errors in JSON format. This middleware should be use at the end of the middleware's chain inside the express app.

Routes

  • routes.express returns an Express instance
  • routes.health returns a microcosm-compatible health check endpoint
  • routes.notFound return a 404-generating endpoint
  • routes.unauthorized return a 401-generating endpoint

Commands

  • install: Install dependencies and save to yarn.lock file
  • lint: Runs airbnb flavored eslint
  • build: Runs tests and transpiles ES6 -> ES5
  • test: Runs tests
  • test:watch: Runs tests watching files changes

Errors

Endpoints should throw errors when something fails. Within nodule-express, it is expected that:

  • All errors define code that can be used by API consumers for error handling business logic
  • Most errors will borrow from HTTP error codes (because they have well-known, useful semantics)
  • Error codes should be visible to API consumers via error.extensions

Local Development

Local development of nodule-express with other repos has a few common pitfalls related to the usage of peer dependencies:

  • nodule-config is a peer-dependency because various libraries act as plugins to it and it needs a single import of bottlejs to share plugin state

To work with nodule-express locally:

  1. Run yarn build within nodule-express to transpile the source.

  2. Change directories to your local repo that you want to test against nodule-express.

  3. Run yarn add /path/to/nodule-express to copy the transpiled source into your local repo. Do NOT use yarn link

  4. After running yarn add, remove (or move-of-the-way) the nodule_modules from within nodule_modules/@globality/nodule-express/