Indexed by TopGit from live GitHub metadata: http-party/registry-mock has 0 stars, written primarily in JavaScript.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
var registryMock = require('registry-mock');
registryMock({ http: 8080 }, (err, registry) => {
if (err) { /* handle me */ }
console.log('Mock npm registry listening on 8080');
});
registry-mock is designed to be a generic caching HTTP server for asserting that proxied
npm registry HTTP calls send the correct payloads and/or headers to the target registry.
In order to test some npm-specific routes (such as publish) it is necessary to cache tarballs
and later serve them.
HTTP & cache conventions
The response to incoming requests can be summarized based on a few simple rules:
All requests to /.*tgz or those with the X-FETCH-CACHE header
respond with the last request body received for that route.
If there is no cache for that route a 404 is served.
If X-CLEAR-CACHE is provided to a cache hit request, then
the cache is cleared for that route.
All other requests are cached for future assertion
and the response is given from the JSON parsed
X-SEND-RESPONSE header:
npm publish PUT /:pkg splits out the tarball and makes
the cache for /:pkg/-/:pkg-:version.tgz available for
download.
Using npm-registry-echo
This package also ships a binary named npm-registry-echo this program runs a simple
registry-mock server and then fetches the cache immediately after all requests. This
allows for simple introspection of the payloads that are sent from the npm CLI.
e.g. Viewing npm publish payloads
1. Running npm-registry-echo
$ npm i -g registry-mock
$ npm-registry-echo
npm-registry-echo listening on 3676
PUT /test-publish03 {"_id":"test-publish03","name":"test-publish03","description":"Just a
test","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"test-publish03","version":
"1.0.0","description":"Just a test","main":"index.js","scripts":{"test":"echo \"Error: no test
specified\" && exit 1"},"author":"","license":"ISC","readme":"ERROR: No README data found!",
"_id":"[email protected]","_shasum":"6e78734fff0347a9596abb5d3b0360fda6f1a899","_from":".",
"_npmVersion":"3.7.1","_nodeVersion":"4.2.2","_npmUser":{"name":"garbage!!user","email":
"[email protected]"},"maintainers":[{"name":"garbage!!user","email":"[email protected]"}],
"dist":{"shasum":"6e78734fff0347a9596abb5d3b0360fda6f1a899","tarball":
"http://localhost:3676/test-publish03/-/test-publish03-1.0.0.tgz"}}},"readme":"ERROR:
No README data found!","maintainers":[{"name":"garbage!!user","email":"[email protected]"}],
"_attachments":{"test-publish03-1.0.0.tgz":{"content_type":"application/octet-stream",
"data":"{{BIG-BASE64-TARBALL}}","length":568}}}
Yes — http-party/registry-mock ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/http-party/registry-mock.
What is http-party/registry-mock?
http-party/registry-mock (http-party/registry-mock) is a JavaScript project tracked by TopGit. The repository has 0 GitHub stars at the time of our last sync.
Where do I read more about http-party/registry-mock?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/http-party/registry-mock is the definitive source.
Read full README in the tab above.
Want a second opinion on registry-mock?
Ask an AI that can read this page — one click and you get its take on registry-mock.
/registry-mock