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.

Sign up for GitHub

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

Jump to bottom

[BUG] npm explore now contains additional output which was not there before #7436

Closed
2 tasks done
dominykas opened this issue Apr 29, 2024 · 1 comment
Closed
2 tasks done

[BUG] npm explore now contains additional output which was not there before #7436

dominykas opened this issue Apr 29, 2024 · 1 comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x

Comments

@dominykas
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

❯ npm explore eslint -- pwd

> eslint@8.39.0 _explore
> pwd

/Users/Dominykas_Blyze/devel/projects/pkgjs/action/node_modules/eslint

Expected Behavior

Same as in 10.5.0:

❯ npm explore eslint -- pwd
/Users/Dominykas_Blyze/devel/projects/pkgjs/action/node_modules/eslint

There are workarounds ofc, but the additional output makes npm explore a lot less useful for scripting things.

Steps To Reproduce

See above

Environment

  • npm:
  • Node.js:
  • OS Name:
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here
@dominykas dominykas added Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x labels Apr 29, 2024
@dominykas
Copy link
Author

Oh, I see #7421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 10.x
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dominykas