napa + npm shrinkwrap incompatible?
See original GitHub issue"napa": {
"malihu-scrollbar": "malihu/malihu-custom-scrollbar-plugin#2.8.3",
"bxslider": "wandoledzep/bxslider-4#798eda1d14b108d8be8f0ab3ec2a2fb4a41ed6d7",
"swfobject": "swfobject/swfobject#a22b7db077abc126d6aa5f2d0f44b11e4ed97940",
"hint": "chinchang/hint.css#v1.3.1",
"colorbox": "jackmoore/colorbox#1.5.9",
"jquery-hashchange": "cowboy/jquery-hashchange#0310f3847f9010faefa0b6abfcf56e8103096192",
"jquery-migrate": "appleboy/jquery-migrate#1.2.1",
"html5shiv": "aFarkas/html5shiv#3.7.2",
"ladda": "hakimel/Ladda#0.9.3",
"modernizr": "Modernizr/Modernizr#v2.8.1"
},
npm ERR! Error: Problems were encountered
npm ERR! Please correct and try again.
npm ERR! extraneous: html5shiv@3.7.2 /Users/kud/Projects/_playmedia/desktop/node_modules/html5shiv
npm ERR! extraneous: hint@1.3.1 /Users/kud/Projects/_playmedia/desktop/node_modules/hint
npm ERR! extraneous: Ladda@0.9.3 /Users/kud/Projects/_playmedia/desktop/node_modules/ladda
npm ERR! invalid: Ladda@0.9.3 /Users/kud/Projects/_playmedia/desktop/node_modules/ladda
npm ERR! missing: spin.js@^2.0.0, required by Ladda@0.9.3
npm ERR! at shrinkwrap_ (/usr/local/lib/node_modules/npm/lib/shrinkwrap.js:30:15)
npm ERR! at /usr/local/lib/node_modules/npm/lib/shrinkwrap.js:24:5
npm ERR! at /usr/local/lib/node_modules/npm/lib/ls.js:44:30
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:130:5
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:258:14
npm ERR! at cb (/usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/slide/lib/async-map.js:48:11)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:258:14
npm ERR! at cb (/usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/slide/lib/async-map.js:48:11)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:258:14
npm ERR! at cb (/usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/slide/lib/async-map.js:48:11)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "shrinkwrap"
npm ERR! cwd /Users/kud/Projects/_playmedia/desktop
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.10
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/kud/Projects/_playmedia/desktop/npm-debug.log
npm ERR! not ok code 0
Issue Analytics
- State:
- Created 9 years ago
- Comments:26 (4 by maintainers)
Top Results From Across the Web
Developers - napa + npm shrinkwrap incompatible? - - Bountysource
Coming soon: A brand new website interface for an even better experience!
Read more >npm prune removes napa packages · Issue #22 · shama/napa · GitHub
When you do npm prune, it removes packages installed by napa. It's a nonsense as it's defined in napa key in ... napa...
Read more >Use Bower packages like npm packages - Rico Sta. Cruz
not compatible with npm shrinkwrap; upgrading packages are not automatic. You have just read Use Bower packages like npm packages, written on ...
Read more >napa - npm
A helper for installing repos without a package.json with npm. ... Start using napa in your project by running `npm i napa`.
Read more >Untitled
Node connectivity diagram, Autotrasporti cardosi livorno, Vallonernas utseende, ... Bonsinvestimentos, Shrink wrap tape for boats, Aye kerunene, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@thanpolas You could do that before I believe; the issue comes into play when there is no package.json. Unless I’m mistaken.
@caseyWebb i did the same thing to my webpack config. nice to know others think along the same lines. also happy that webpack supported this unique requirement with minimal effort.