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

modules-middleware

v0.7.3

Published

express middleware for serving npm modules to client side

Downloads

5

Readme

modules-middleware

NPM Version

Express middleware for serving node modules to client side.
Useful for serving client side apps structued as node module package, containing a package.json and dependencies.

modules-middleware:

  • Serves sources and static assets from the module directory
  • Serves sources and static assets of module dependencies defined in package.json (resolves using node's require.resolve starting from the module directory)
  • works with monorepos
  • transforms package names to valid browser ES6 paths when serving .js, .jsm and .html source files of the module and dependencies. for example, a js module containing an ES6 import such as:
    import { PolymerElement } from '@polymer/polymer'; will transform into
    import { PolymerElement } from '/node_modules/@polymer/polymer/';
    • Support node.js require() flexibility, (omitting .js extension, specifying directory name only to serve a contained index.js file, etc..)
    • Multiple packages sharing the same dependency at the same version will result in the same client url (for caching)
    • Multiple packages sharing the same dependency with different versions will result in a different client url

Install

$ npm install modules-middleware

or

$ yarn add modules-middleware

API

var modulesMiddleware = require('modules-middleware')

modulesMiddleware(modulePath, options)

Create a new middleware function to serve files from within a given module path.

Options

modulesDirectoryUrlName

The prefix of packages urls for transformed client side sources, defaults to "node_modules".

Serving using express

This is a simple example of using Express.

var express = require('express')
var modulesMiddleware = require('modules-middleware')

var app = express()

app.use(modulesMiddleware('./frontend'));
app.listen(3000)

with monorepo

if you are using a monorepo containing a package of your client side code you may use require.resolve as the module path

var express = require('express')
var modulesMiddleware = require('modules-middleware')

var app = express()

app.use(modulesMiddleware(require.resolve('my-client-app'));
app.listen(3000)

License

MIT