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: npm uses a package from the top level directory, not from its own. #1537

Closed
akopchinskiy opened this issue Jul 19, 2020 · 1 comment
Closed
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@akopchinskiy
Copy link

akopchinskiy commented Jul 19, 2020

What / Why

npm for some reason, it uses a package from the top level directory, not from its own.
Ambiguous behavior, seems like a bug.

When

/main-project
├─── /node_nodules
├─── /webpack@4
├─── package.json
└─── /sub-project
│      ├── /node_nodules
│      ├── /webpack@3
│      └── package.json

Where

  • n/a

How

Steps to Reproduce

cd .../sub-project
Run script react-scripts from here (/sub-project).
Read error.

Current Behavior

It's using package from folder /main-project
Giving error: You have installed webpack@3 in /main-project

Expected Behavior

It's using package from /sub-project.
No errors, obviously.

@darcyclarke darcyclarke added Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release labels Oct 30, 2020
@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