-
-
Notifications
You must be signed in to change notification settings - Fork 303
iojs-full without upgraded npm #1
Comments
That's a bit strange – so you can't update npm at all? That sounds like a bug with npm and/or io.js – why would it suddenly stop working if it updates? You sure that node-gyp works fine on Alpine Linux in the first place? I suspected that musl libc prevented many native modules from building at all. Have you got an easy way to reproduce this? |
I can use npm, i can't use packages that use node-gyp. It's a bug with node-gyp that's fixed in the npm version bunded with io.js. (nodejs/node-gyp#564, nodejs/node#433) It works just fine if i copy your dockerfile and remove the Repro something like:
|
Although now i end up with a 400mb image, so not a huge gain anymore. |
Ok cool – I'll look into this and let you know if I come up with something better! |
I think that removing the npm upgrade and letting users do it themselves seems fine, but that's up to you obviously. |
Well I think a solution that allows the latest version of npm is best – I mean, it doesn't make sense to have to be stuck on an old version and not be able to upgrade. |
Of course, but the user can always run |
Well, I've rebuilt and pushed as |
It does, thank you. |
node-gyp will fail in a lot of cases if one doesn't use the npm bundled with iojs.
It would be great to be able to use your alpine-iojs package but without the
npm update -g npm
part here: https://github.com/mhart/alpine-node/blob/master/Dockerfile.full#L21The text was updated successfully, but these errors were encountered: