Created
June 3, 2015 13:05
-
-
Save lennym/471115da5902b308cc7e to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11:22 AM <lennym> Morning all, I'm having some issues with node-sass and npm, but only in certain contexts. I was hoping to talk it through to see if I'm doing anything obviously stupid. | |
11:23 AM <lennym> I have a project, which has a module as a dev dependency - both depend on node sass, and both run node sass as part of a postinstall script | |
11:24 AM <lennym> Except the postinstall script fails in node-sass for the child module with an error of "Cannot find module semver" here - https://github.com/sass/node-sass/blob/v2.1.1/lib/extensions.js#L1 | |
11:24 AM <lennym> When run not as a child dependency of the parent project it works fine. | |
11:24 AM <lennym> Both projects have the same (2.1.1) dependency of node-sass | |
11:25 AM <lennym> Now here's the kicker... it *only* fails as part of an npm install on our jenkins build server, I can't replicate locally. | |
11:26 AM <lennym> If anyone has any ideas or suggestions I'd be happy to hear them. | |
11:31 AM <lennym> npm 2.7.6 on our jenkins box, 2.9.1 locally | |
11:31 AM <lennym> And looking at the content of node_modules, node-sass and semver are both there in a location which should be resolvable from the child module |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment