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 🙏

© 2025 – Pkg Stats / Ryan Hefner

norajs

v1.0.6

Published

Simple & Sweet services

Downloads

13

Readme

Nora.js Build Status

Sweet, simple express services

A sweet, simple, express-oriented framework for quickly hammering out ES7-style services. Convention over configuration, but hardly any of either, Nora is aware of a Server, Configurations and Services – with the server representing your app.

In terms of lifecycle, Nora apps typically do the following:

  • Spin up a Server, which can configure Express as needed
  • Add Configurations, potentially instantiating DB connections, wiring up Express routes, etc
  • Add Services, which do the business logic of your application
  • Start express by listening on the designated port (5000 by default)

Configurations have a two-step lifecycle, Configuration.preConfigure and Configuration.postConfigure respectively. The difference between the two is that the latter is called after all configs have had their Configuration.preConfigure methods run and all services have had their Service.configure methods run – allowing services to be retrieved by name.

A simple example:

svc/DummyService.js:

const nora = require('norajs')
class DummyService extends nora.Service {

  postConfigure(server){
    this.logger.info('Configured!')
  }

  doSomething(){
    return 'Dummy service did something!'
  }
}

module.exports = new DummyService()

app.js:

const nora = require('norajs')
class DummyRouter extends nora.Configuration {

  postConfigure(server, config, idx){
    const { app } = server         
    const { DummyService } = server.named

    const router = nora.Router()
    router.get('/dummy', async (req, res, next) => {
      res.send({name: 'Jimbo Jones', message: DummyService.doSomething() })
    })

    app.use('/test', router)
  }
}

const server = new nora.Server({
  basePath: __dirname,
  nora: { autoscan: true }
})
server.addConfig(new DummyRouter())
server.start()

Note that we specified autoscan: true on the server's nora property, allowing nora to scan both the ./config and ./svc folders for Services and Configurations respectively.