[BUG] ENOENT: no such file or directory

[kubilaysargin]

I have a problem while installing react-native-cli. When i type npm install -g react-native-cli it gives me so much no such file or directory errors. One example is ENOENT: no such file or directory, open 'C:\Users\KUBİLAY\AppData\Roaming\npm\node_modules.staging\winston-6bc268e1\test\transports\webhook-test.js'. When look this winston-6bc268e1 folder's inside, first name of folders are deleted(like est for test, ib for lib).

[DanielRuf]

This is probably an issue with your username (special characters and spaces).

Duplicate of #417

[rushilsrivastava]

It's an issue with package-lock.json. Deleting it and clearing npm cache will fix the issue.

[DanielRuf]

It's an issue with package-lock.json. Deleting it and clearing npm cache will fix the issue.

Not in all cases. This can help as it refetches packages and updates the dependencies so a fresh cache is used.

You can also use npm i --force.

[rushilsrivastava]

You can also use npm i --force .

I can confirm that npm i --force does not work in this situation. The only work around seems to be deleting the package lock.

[olavfosse]

bump. can you please fix this, it has persisted for soon 4 years and been reported numerous times. It has surely affected a lot of people through the years.

https://github.com/zkat/npx/search?o=asc&q=space+windows&s=created&type=issues
https://github.com/npm/npx/search?q=space+windows&type=issues
https://github.com/npm/cli/search?q=space+windows&type=issues

Thanks

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

[olavfosse]

This bug has been discarded maybe 100 times now. Please re-open.

[olavfosse]

@isaacs @iarna @zkat

Please reopen this.

[ljharb]

@fossegrim does it still occur on npm 7?

[olavfosse]

yes

[darcyclarke]

@ljharb we're closing this as the codebase changed significantly between 6-7 - @fossegrim can you please create a new issue w/ more information about the specific problem you're seeing in v7

[ljharb]

@darcyclarke i'm not sure why the codebase changes would have any bearing on the reported problem, which the OP claims still occurs in npm 7.

[olavfosse]

Steps to reproduce from what I remember is:

1. Create user with username containing space, for example "Olav Fosse". (by default the installer infers username from email. To make the installer prompt for a username string you have to tell it that you cannot connect to internet).
2. Install npm
3. Try doing something with npm. I think I tried running cra npx create-react-app appname or something like that. Everything I ran failed.

[olavfosse]

I cannot be bothered to install Win10 and make a proper detailed bug report, because every time this has been reported previously the issue has been closed prematurely.