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

svr

v2.3.28

Published

HTTP development server done right

Downloads

299

Readme

Last version Build Status Dependency status Dev Dependencies Status NPM Status

HTTP development server done right.

Features

  • Smart reload, just reloading modified files to do development fast.
  • Reload on demand, after type rs on your terminal.
  • Pretty Errors, making unexpected errors easy to read.
  • Port Selection, supporting detection for already in use ports.
  • Clipboard Support, copying the local address in your clipboard.
  • Debug in Your Network, exposing the process in your local network.

It's similar micro-dev, but compatible with any function that exposes req, res interface (micro, express, koa, hapi, fastify, etc).

Installation

$ npm install svr --save

Usage

Defining entry point

Create a file and export a function that accepts the standard http.IncomingMessage and http.ServerResponse objects, that means, the exported function should be receive req, res:

const express = require('express')
const { Router } = express
const router = Router()

// define middlewares
router.use(require('helmet')())
router.use(require('compression')())
router.use(require('cors')())

// define routes
router.get('/', (req, res) => res.status(204).send())
router.get('/robots.txt', (req, res) => res.status(204).send())
router.get('/favicon.txt', (req, res) => res.status(204).send())

// expose router
module.exports = router

After that, just call svr:

$ svr

svr is assuming you have a main file declared in your package.json in the project directory. Also, you can provide it as first argument:

$ svr index.js

We recommend setup svr as npm script:

{
  "scripts": {
    "dev": "svr"
  }
}

Now, running npm run dev it will be start your HRM development server:

$ npm start

  ┌───────────────────────────────────────────────────┐
  │                                                   │
  │   my-express-api is running!                      │
  │                                                   │
  │   • Local:            http://localhost:3000       │
  │   • On Your Network:  http://192.168.1.106:3000   │
  │                                                   │
  └───────────────────────────────────────────────────┘

You can type svr --help to see all the options.

Smart Reload

When a file is modified in the project directory, svr will reload just the modified file:

  ┌───────────────────────────────────────────────────┐
  │                                                   │
  │   my-express-api is running!                      │
  │                                                   │
  │   • Local:            http://localhost:3000       │
  │   • On Your Network:  http://192.168.1.106:3000   │
  │                                                   │
  └───────────────────────────────────────────────────┘

   ℹ 18:32:42 modified index.js

Also, svr takes into consideration files that can be ignored:

  • Well known files to ignore, like node_modules, .git, etc.
  • .gitignore declarations.
  • ignored field in your package.json.

If you need to add a specific file to ignore, use i or --ignore flag:

$ svr -i .cache -i public

Also, you can use -w or --watch to add more file path to be listened. You can declare:

  • Relative or absolute paths.
  • Glob patterns.

Reload on demand

In any moment you can refresh the process typing rs in the terminal window where svr is running:

  ┌───────────────────────────────────────────────────┐
  │                                                   │
  │   my-express-api is running!                      │
  │                                                   │
  │   • Local:            http://localhost:3000       │
  │   • On Your Network:  http://192.168.1.106:3000   │
  │                                                   │
  └───────────────────────────────────────────────────┘

   ℹ 18:32:42 modified index.js
   rs
   ℹ 18:34:07 restart index.js

Don't use on production

svr is oriented just for development scenarios, not for production.

Under production, simply create the server you need based on your necessities, for example, let's create a bin/server as production server:

#!/usr/bin/env node

'use strict'

const express = require('express')

const app = express()

require('./index')(app, express)

const port = process.env.PORT || process.env.port || 3000
const { name } = require('../package.json')

app.listen(port, function () {
  console.log(`${name} is running at http://localhost:${port}`)
})

You can declare it as npm start script:

{
  "scripts": {
    "dev": "svr",
    "start": "bin/server"
  }
}

That's all.

License

svr © Kiko Beats, released under the MIT License. Authored and maintained by Kiko Beats with help from contributors.

kikobeats.com · GitHub Kiko Beats · Twitter @Kikobeats