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

@despel/live-reload-api

v1.1.1

Published

## How to Use

Downloads

3

Readme

Simple Module for Reloading Stateless API Endpoints on File Changes

How to Use

const app = express()

const API_PATHS = [
  '/src/api',
  '/src/new_api',
]

const API_PREFIXES = [
  '/v1',
  '/v2',
]

const loadedCallback = () => {
  console.log('Endpoints loaded!')
}

const { setupAPI } = require("@despel/live-reload-api")
const reloadAPI = setupAPI(app, API_PATHS, API_PREFIXES, loadedCallback)

After saving a file inside the API_PATHS folder, the entire API will be reloaded. Creating and deleting files also updates the API.

How to create an endpoint

Endpoint URL

The file path wil determine the endpoint path, for example

  url = 'http://localhost:3434'
  apiPrefix = '/session'
  apiPath = '/api/src/session'
  filePath = '/api/src/session/users/create.js'

The resulting endpoint will be:

  url + apiPrefix + filePath.replace(apiPath, "")
  // http://localhost:3434/session/users/create

Endpoint file structure To correctly create an endpoint, the following structure is required

module.exports = {
  // optional, use at least one
  get: {
    function: (req, res) => {}, // Request handler
    middleware: [ // Middeware applied to the specific endpoint method
      (req, res, next) => {},
      //... 
    ]
  },
  post: {
    function: (req, res) => {},
    middleware: [
      (req, res, next) => {},
      //... 
    ]
  },
  put: {
    function: (req, res) => {},
    middleware: [
      (req, res, next) => {},
      //... 
    ]
  },
  delete: {
    function: (req, res) => {},
    middleware: [
      (req, res, next) => {},
      //... 
    ]
  },
  // Middleware applied to all methods
  middleware: [
    (req, res, next) => {},
    //... 
  ]
}

Middlware It is recommended to put the middleware in a different file/folder. The middleware for the endpoints is inherited from the folder structure.

If a parent folder contains a middleware.js file, the defined handlers will be applied to all children endpoints.

Middleware.js file structure

module.exports = {
  middleware: [ // Applied to all methods (general middleware).
    (req, res, next) => {},
    // ...
    (req, res, next) => {},
  ],
  get: [ // Applied only to a specific method (specific middleware).
    (req, res, next) => {},
    // ...
    (req, res, next) => {},
  ],
  //... post, put, delete
}

The order of execution of the middleware starts from the root folder and the general middleware is executed before the specificic middleware. The file middlware.js is prepended to the middleware specified in endpoint_name.js.