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]: unable to link puppeteer #7753
Comments
I think it is because this #7727 adding husky call here https://github.com/puppeteer/puppeteer/blob/v11.0.0/package.json#L20 |
@pawel-id I'm having the same issue with a similar workflow. Did you find a way around this? |
@timmhayes workaround: install husky globally before puppeteer |
@pawel-id Thanks, I'll give that a try. |
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it! |
Bug description
Steps to reproduce the problem:
npm install -g puppeteer@11.0.0
npm init --yes
npm link puppeteer
fails with an errorsh: husky: command not found
The error is not happening on previous puppeteer versions.
This kind of setup we are using to have single global puppeteer within docker and few node projects reusing the global puppeteer to keep docker image reasonably small size.
Puppeteer version
11.0.0
Node.js version
v14.17.4
npm version
7.24.2
What operating system are you seeing the problem on?
Linux, macOS
Relevant log output
The text was updated successfully, but these errors were encountered: