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
"ENOENT: no such file or directory, rename ..." when running npm install #890
Comments
Ugh, I thought this was solved. See #866. So, it errors on first run? Can you test again? Make sure you delete any |
It gives me the errors on subsequent runs after the first install. (I'll edit the original post a bit to be more clear) |
Thanks @Ionaru. I was able to replicate an error on second run with |
I am already using NPM 5.4.2 (See log output and environment info) 😉 |
oh, sorry I missed that. hmmm. |
Any luck reproducing the issue? Let me know if you need more information. |
+1 |
Yes, I was able to replicate. However I'm not sure how to fix. So, anyone hitting this the workaround are:
|
Another workaround is to pin your sqlite3 version to the last one without this issue (v3.1.11): |
Pinned sqlite3 to 3.1.11 because this version doesn't make trouble. TryGhost/node-sqlite3#890 Zeilen,
Can everyone hitting this error test again with the newly released |
I just tested with The original issue was from a Linux system, I won't be able to test it on that until tomorrow. |
Great, thanks for the prelim testing. Look forward to your results for windows tomorrow. |
|
Great. Thanks for the followup @Ionaru |
In my Windows 7, the error is solved by adding |
Same as closed issue #866, looks like regression.
First npm install (No package-lock.json and node_modules folder in project)
Run
npm install
again (package-lock.json and node_modules folder now exist in the project)Run
npm install
another timeEnvironment
Sqlite 3.1.12
Node 8.5.0
NPM 5.4.2
The text was updated successfully, but these errors were encountered: