Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reggie fails registering repository #45

Open
OliverZ opened this issue Mar 14, 2014 · 2 comments
Open

reggie fails registering repository #45

OliverZ opened this issue Mar 14, 2014 · 2 comments

Comments

@OliverZ
Copy link

OliverZ commented Mar 14, 2014

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 by a nodejs version greater than 0.10.23.

when publishing there is no error on the client, everything seems ok. But when I try to install my repository which was created with nodejs v0.10.26 there is some error with the version number:

c:\Development\temp>npm i n26test
npm WARN package.json [email protected] No repository field.
npm http GET http://npm.mydomain.com/n26test
npm http 200 http://npm.mydomain.com/n26test
npm ERR! notarget No compatible version found: n26test@'*'
npm ERR! notarget No valid targets found.
npm ERR! notarget Perhaps not compatible with your version of node?
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "n26test"
npm ERR! cwd c:\Development\temp
npm ERR! node -v v0.10.23
npm ERR! npm -v 1.3.17
npm ERR! code ETARGET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     c:\Development\temp\npm-debug.log
npm ERR! not ok code 0    
@matthiasg
Copy link

can you post the package.json please ? its a little confusing to see two different package names. maybe you made a publishing error ? the exact sequence of commands is also helpful.

c:\Development\temp>npm i n26test
npm WARN package.json n23test@0.0.0 No repository field.

@OliverZ
Copy link
Author

OliverZ commented Mar 17, 2014

the package.json (I did the file with the "npm init" command) looked like:

{
  "name": "n26test",
  "version": "0.0.0",
  "description": "testing publishing with node 0.10.26",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "Oliver",
  "license": "ISC"
}

The warning comes from my client machine, because earlier I installed the repository "n23test". And this repository was also in "c:\Development\temp". If I install "n26test" from another directory, the warning

npm WARN package.json [email protected] No repository field.

dissapears, but the same error with the version number as above still exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants