Registry / web-framework / npm-http-server

npm-http-server

library4.3.0jsnpmunverified

HTTP server that serves files from npm packages by URL pattern /package@version/path. Current stable version 4.3.0. Designed for development or mirroring npm package contents over HTTP. Supports version ranges, tagging, automatic index generation, and optional Bower bundle creation. Pre-ESM, CommonJS-only module with named exports. Last published 2019; no recent updates. Differentiates from nginx-static or serve by resolving npm registry versions dynamically.

web-framework http-networking

npm install npm-http-server

github ↗package ↗

INSTALL

IMPORT

SIG · NPM-HTTP-SERVER

npm-http-server

web-frameworkjavascriptv4.3.0

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

createServer

✓ import { createServer } from 'npm-http-server'

✗ import createServer from 'npm-http-server'

Named export, not default. CommonJS: const { createServer } = require('npm-http-server')

createRequestHandler

✓ import { createRequestHandler } from 'npm-http-server'

✗ const createRequestHandler = require('npm-http-server').createRequestHandler

Exported as named. No default export.

npm-http-server

✓ import * as NpmHttpServer from 'npm-http-server'

✗ import NpmHttpServer from 'npm-http-server'

Namespace import works but no default export.

Creates a server that serves package.json from any npm package by URL.

import { createServer } from 'npm-http-server'; const server = createServer({ registryURL: 'https://registry.npmjs.org', autoIndex: true }); server.listen(8080, () => { console.log('npm-http-server running on port 8080'); }); // Then visit: http://localhost:8080/express@4.18.2/package.json

npm-http-server --version

Debug

Known issues

deprecatedPackage is in maintenance mode; last release 2019, no updates for security or modern npm registry changes.

fix

Consider alternatives like unpm or unpkg for similar functionality.

affects: >=1.0.0

gotchaNo default export; must use named imports `{ createServer }`.

fix

Use `import { createServer } from 'npm-http-server'` or `const { createServer } = require('npm-http-server')`.

affects: >=1.0.0

gotchaRequires a running npm registry; offline or private registries need custom registryURL.

fix

Set `registryURL` to your registry's URL in createServer options.

affects: >=1.0.0

breakingRemoved bower support default; bowerBundle option must be explicitly set.

fix

Set `bowerBundle: '/bower.zip'` in options if needed.

affects: >=4.0.0

deprecatedBower support is discouraged; documentation advises against using Bower.

fix

Use webpack or browserify instead for asset bundling.

affects: >=4.0.0

Errors

Common errors & fixes

Cannot find module 'npm-http-server'

Package not installed or wrong import syntax.

fix

Run `npm install npm-http-server` and ensure correct import: `import { createServer } from 'npm-http-server'`.

TypeError: npm_http_server_1.createServer is not a function

Default import used instead of named import.

fix

Change `import createServer from 'npm-http-server'` to `import { createServer } from 'npm-http-server'`.

Error: Cannot resolve registryURL

Invalid or missing registryURL option.

fix

Provide a valid registry URL, e.g., `registryURL: 'https://registry.npmjs.org'`.

Error: package not found

Package name or version does not exist in registry.

fix

Verify the package name and version are correct and published to the configured registry.

Upgrade

Version history

4.3.0latest on npm

Audit

Dependencies

expressoptionalOptional integration for middleware usage

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/unpkg/npm-http-server ↗

packagehttps://www.npmjs.com/package/npm-http-server ↗