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

@nicolasparada/web-framework

v0.8.2

Published

HTTP Web Framework

Downloads

7

Readme

@nicolasparada/web-framework npm version dependencies

Minimalistic Node.js HTTP Web Framework.

const framework = require('@nicolasparada/web-framework')

const app = framework()

const getNameMiddleware = (req, next) => next(req.params.name)
const hello = name => `Hello, ${name}!`

app.get('/hello/:name', getNameMiddleware, hello)

app.listen(80, '127.0.0.1', () => {
  console.log('Server running at http://localhost/hello/world 🚀')
})

This framework sets trivials headers for you, so you can simply return any value, but if you want to respond with a custom status code or headers, make sure to return a object with a statusCode number and a headers plain object. body can take any value.

app.get('/advanced', () => ({
  statusCode: 418,
  headers: {
    foo: 'bar'
  }
}))

You should have your tipical routing capabilities: get, post, put, patch, delete and options. It uses the path-to-regexp engine to parse the pattern (same as express or react-router).

match allows you to catch various HTTP verbs.

app.match(['PATCH', 'PUT'], '/pattern', updateHandler)

any catches all HTTP verbs.

requestHandler is useful if you want to use your own server. Just attach it to the request event.

const fs = require('fs')
const https = require('https')
const framework = require('@nicolasparada/web-framework')

const app = framework()

const options = {
  key: fs.readFileSync('key.pem'),
  cert: fs.readFileSync('cert.pem')
}

const server = https.createServer(options)
server.on('request', app.handleRequest)
server.listen(443, '127.0.0.1', () => {
  console.log('Server running at 🔒 https://localhost/ 🚀')
})

listen returns http.Server.

You can register global middlewares passing them to the framework constructor.

const delay = ms => new Promise(resolve => {
  setTimeout(resolve, ms)
})

const delayMiddleware = async (req, next) => {
  const ms = parseInt(req.query.delay, 10)
  await delay(ms)
  return next(req)
}

const app = framework([delayMiddleware])

Tip! You can add middlewares later in the pipeline thanks to async/await.

const afterMiddleware = async (req, next) => {
  const res = await next(req)
  // Do something here
  return res
}

Middlewares