node-reggie
node-reggie copied to clipboard
mbrevoort
An experimental light weight alternative to a full blown npm registry
This error is thrown from restify's dependency. This PR changes restify for express. Resolves #56
Command reggie-server -d ~/.reggie fails with error. **node version**:v7.7.1 v8.1.1 **OS**: ubuntu 16.10 **Complete stacktrace**: ``` util.js:955 throw new TypeError('The super constructor to "inherits" must not ' + ^ TypeError:...
Throws error when calling reggie-server -h ``` (node:12440) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent...
NPM will complain if one try to publish an package with the same version number as a previously published package: Example: ``` npm ERR! publish fail Cannot publish over existing...
When running reggie-server on node versions higher than 0.10.23 which uses npm 1.3.21 it just fails silently. ``` npm http PUT http://localhost:8082/delegator/-/delegator-0.0.6.tgz/-rev/1-0 npm http 201 http://localhost:8082/delegator/-/delegator-0.0.6.tgz/-rev/1-0 npm http PUT http://localhost:8082/delegator/0.0.6/-tag/latest...
On the client, I ran reggie publish: ` %reggie -u http://127.0.0.1:8280 publish uid2-0.0.2.tgz successfully published version 0.0.2 of uid2: http://127.0.0.1:8125/package/uid2/0.0.2 done ` On the server side, an error is written...
I'm using reggie with the proxy npm module "kappa" on my server.If I publish a package to my private npm repository server, reggie fails registering it, if it was published...
I want to maintain a "snapshot" of packages I use for my products, as well as its dependencies. Is it possible ?
Hi, the idea is to add the support for **npm adduser** and **npm owner** interfaces (which already support --registry), and protect write APIs enforcing authentication by default. I am assuming...
Hi, Reggie should implement support for **npm tag** - eg. _npm tag [email protected] edge --registry=http://0.0.0.0:8080/_