not found by npm, latest release fails to install

[alexfernandez]

[email protected] not found by npm, latest release fails to install

[zdj]

just create a new npm project and then try to install the latest version of loadtest.

[zdj]

a workaround is to install from the stdio 0.2.1 tar directly prior to installing loadtest: npm install https://github.com/sgmonda/stdio/archive/0.2.1.tar.gz --save

[alexfernandez]

I have just installed it successfully:

$ npm install loadtest
npm http GET https://registry.npmjs.org/loadtest
npm http 200 https://registry.npmjs.org/loadtest
npm http GET https://registry.npmjs.org/log
npm http GET https://registry.npmjs.org/prototypes
npm http GET https://registry.npmjs.org/testing
npm http GET https://registry.npmjs.org/stdio
npm http GET https://registry.npmjs.org/agentkeepalive
npm http 200 https://registry.npmjs.org/agentkeepalive
npm http 304 https://registry.npmjs.org/prototypes
npm http 304 https://registry.npmjs.org/log
npm http 200 https://registry.npmjs.org/stdio
npm http GET https://registry.npmjs.org/stdio/-/stdio-0.2.3.tgz
npm http 200 https://registry.npmjs.org/stdio/-/stdio-0.2.3.tgz
npm http 304 https://registry.npmjs.org/testing
[email protected] node_modules/loadtest
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

The dependency on stdio is expressed with caret notation: ^0.2.1, which means that any version later than 0.2.1 is fine (such as 0.2.3 above). Can you give me a few more details to pinpoint this issue?

[seriousManual]

which npm version are you on? (npm -v)

up to a certain version the caret notation is not supported, please update npm than.

[zdj]

Well I feel like a dope, I assumed I was on the latest node/npm but my brew update script had been failing for some time due to an Xcode issue. After I updated node/npm, the issue went away. Thanks for pointing out something I really should have researched a bit more.

[alexfernandez]

I am updating the dependency for stdio to 0.2.3 in commit c8cd9bd, in order to work around older npm clients, so that others are not tripped by the same issue. Thanks for the report!

[seriousManual]

it will still break on older npm as you specified the version using a caret, use the tilde instead if you want to be backwards compatible
in my personal opinion updating npm is the right way to solve this issue.

[alexfernandez]

Ah, OK. Just intended as a workaround, but if it does not work then no harm done. Thanks!