-
Notifications
You must be signed in to change notification settings - Fork 117
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
Failed at the expect@1.12.1 postinstall script 'node npm-scripts/postinstall.js' #39
Comments
Thanks for the bug report, @pierol. Can you please paste the result of running |
Thank for your attention @mjackson from inside the repo root the error of
is
|
I meant from inside the expect repo root. :) Or maybe the problem is that our |
Sorry @mjackson i'm not an expert of npm packages but the error came out when i did a npm install of a react boilerplate project that i downloaded from github. I don't have a npm-scripts folder in the root repo of my project. The package i think should install locally as a result of the npm install comand. |
No problem, @pierol. Please try |
Yes doing a npm install of the single package went good, so as you suggest the problem is not your package. |
We have the same problem here. doing Definitely a problem related to installing expect at the same time as other modules. |
I bet we need to change |
why not just: "postinstall": "npm run build" |
@rstacruz I think if we do that then people who don't get our devDependencies (i.e. people who install using Regarding win-spawn, does |
Any updates @pierol? I'd like to close this if we can. Thanks. |
Hi @mjackson sorry for the late, i download a new fresh copy of the package react-redux-webpack-boilerplate-master and i edit the package.json and update the expect package version to 1.12.2 but the error happen again here the erro log:
|
Thanks for reporting back @pierol. The |
@mjackson i'm sure i have the rights for that, i'm under windows file system and i have administration rights (on windows system we don't have the sudo command a npm install is enough if you are an administration user of the machine). The installation process create folders under the node_modules of the root repo and for other packages the creation process doesn't stop with an access right error only for the package expect@1.12.2. Look at this snapshot it shows you all the folder starting with 'e' under the node_modules folder of the repo, you can see all the packages needed but you can't find yours: |
I can't see anything else in npm's error message that give me any other Just to be clear, when you do an On Thu, Oct 15, 2015 at 10:26 AM Piero Longhetto notifications@github.com
|
Yes right: it happens only when i do a npm install not when i install only your package. I don't know if you can simulate in some way my process. Could it be the path: different slash on windows platform ? |
Just for information if i do the same operation on a Mac no error comes out. So the problem is specific to windows platform. |
@pierol The comment from @breedx2 suggests that this problem only happens when you install expect along-side other packages. Maybe you could create a test package and try installing some other package and expect in the same go. Something like:
And see what happens? Since I don't have access to a Windows machine, I can't test on my end. |
I create this package.json file: {
"name": "test-package",
"version": "0.0.1",
"description": "test for expect",
"main": "",
"scripts": {
},
"author": "Kevin Whitaker",
"license": "MIT",
"devDependencies": {
"babel": "^5.8.23",
"expect": "^1.12.2"
}
} put it in a folder called test-package and run npm install and no errors appear and the package expect is inside the node_modules of the root test-package. So it's real a strange bug. |
Which original package are you trying to install? |
I just cloned the repo and npm install worked great.
|
Same here.
|
I'm on windows 10 BTW |
Cloned repo, npm install-ed, node-gyp threw a ton of errors but in the end it actually seemed to build fine. Windows 10 |
about node-gyp: nodejs/node-gyp#629 |
@luisrudge that just ruined my day |
Updated to latest version of npm using "npm i -g npm@latest", re-ran the react-redux-webpack-boilerplate's "npm install" and it worked fine. Also installed the C++ tools for Visual Studio but I'm skeptical that had any impact on the outcome. |
@luisrudge @mindpivot Thank you for testing this out! @pierol I don't know what to tell you. It looks like other Windows users are ok. I'm going to close for now. If you find any new evidence, please comment and we can re-open! |
I'm trying to npm install a project that have your package as dependecy under Windows 7 SP1 x64 ITA but something goes wrong
The text was updated successfully, but these errors were encountered: