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

pnpm exec outputs garbage before running command if .pnpmfile.cjs exists #5027

Closed
anomiex opened this issue Jul 13, 2022 · 2 comments · Fixed by #5032
Closed

pnpm exec outputs garbage before running command if .pnpmfile.cjs exists #5027

anomiex opened this issue Jul 13, 2022 · 2 comments · Fixed by #5032
Assignees
Milestone

Comments

@anomiex
Copy link

anomiex commented Jul 13, 2022

Since 7.5.1, pnpm now outputs some garbage before running the command. This breaks things if the output is being piped into another process.

pnpm version: 7.5.1

Code to reproduce the issue:

Create an empty directory. Run the following:

  1. pnpm add hello-world-npm
  2. echo 'module.exports = {}' > .pnpmfile.cjs
  3. pnpm hello-world-npm

Expected behavior:

Output is

Hello World NPM

Actual behavior:

Output is

Using hooks from: /tmp/test/.pnpmfile.cjs
Hello World NPM

Additional information:

  • node -v prints: v16.16.0
  • Windows, macOS, or Linux?: Linux
@anomiex
Copy link
Author

anomiex commented Jul 13, 2022

Looks like this was a side effect of #5012, output that formerly went to the log file now goes to the console.

@zkochan zkochan self-assigned this Jul 13, 2022
@zkochan
Copy link
Member

zkochan commented Jul 13, 2022

This is the same issue as actions/setup-node#543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants