Skip to content
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

[BUG] inconsistent behavior between Case-sensitive filesystem and non-case-sensitive filesystem #1782

Closed
arily opened this issue Sep 9, 2020 · 2 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@arily
Copy link

arily commented Sep 9, 2020

Current Behavior:

npm will install the local module with inconsistent case in non-case sensitive filesystem

Expected Behavior:

inconsistent should be checked and throw an error when Inconsistent case ( at least should be the default behavior.)

Steps To Reproduce:

let's say we have a local module at /path/to/app/path/to/my/Local_module,
in a non-case-sensitive system install a local module with inconsistent path

npm install Path/tO/mY/lOcAl_Module

would work
but when deploy to an case-sensitive system
npm install will fail with error

npm WARN checkPermissions Missing write access to /path/to/app/node_modules/Path/tO/mY/lOcAl_Module

Environment:

production

  • OS: Ubuntu 20.04
  • Node: 10.16.0
  • npm: 6.13.2

development

  • OS: macOS 10.15.6
  • Node: 12.16.1
  • npm: 6.14.8
@arily arily added Bug thing that needs fixing Needs Triage needs review for next steps Release 6.x work is associated with a specific npm 6 release labels Sep 9, 2020
@arily
Copy link
Author

arily commented Sep 9, 2020

update: "rm -rf node_modules" then re-run "npm install" will fix the problem one time

@darcyclarke
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

2 participants