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

@conjurelabs/mode

v0.2.1

Published

express server scaffolding

Downloads

4

Readme

Mode

Quick setup scaffolding for an Express server

Install

npm -i --save @conjurelabs/route @conjurelabs/utils @conjurelabs/mode

Usage

Add a directory of routes, in ./routes within your project root.

const mode = require('@conjurelabs/mode')
mode()

This will run an Express sever on :3000

See the route module documenation for more deatils on using routes.

Routes within a mode server can access the route module via @conjurelabs/mode/route.

// within './routes/test/get.js'
const Route = require('@conjurelabs/mode/route')

const route = new Route()

route.push(async (req, res) => {
  res.send('Hello')
})

module.exports = route

// this will allow a user to GET /test on the running server

See a working example.

Advanced Usage

Name

You can set a more specific name for your server. This makes logs more sensical when dealing with multiple servers.

mode({
  name: 'API'
})

Routes Directory

By default mode will crawl routes at ./routes within the project root. You can override that.

mode({
  routesDir: '/custom/routes/dir'
})

Port

By default mode runs on port 3000

mode({
  port: 4400
})

Adding more Express configuration

After mode finishes configuring the express server, you can add your own addidtional config.

mode({
  serverAfterConfig: (server, express) => {
    server.use(express.static('public'))
    server.use(passport.initialize())
    server.use(passport.session())
  }
})

Before server starts

This is useful for wrapping .listen with additional logic, like when wrapping Express in a Next app.

mode({
  beforeListen: (server, express, done) => {
    // start next app
    nextApp
      .prepare()
      .then(done)
  }
})

After server starts

mode({
  afterListen: (server, express) => {
    // ...
  }
})