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

fix: run prepublish scripts of packages installed from Git #5837

Merged
merged 14 commits into from Dec 25, 2022
Merged

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented Dec 25, 2022

close #5826

@zkochan zkochan merged commit 339c0a7 into main Dec 25, 2022
@zkochan zkochan deleted the fix/5826 branch December 25, 2022 19:18
@zkochan zkochan added this to the v7.20 milestone Dec 28, 2022
stefanmaric added a commit to MasterworksIO/eslint-config-masterworks that referenced this pull request Jan 10, 2023
Version v7.20.0 of pnpm introduced a change that makes it run our
publish script on install, breaking CI pipelines and local envs
alike.

See: pnpm/pnpm#5837
See: pnpm/pnpm#5826
See: https://github.com/pnpm/pnpm/releases/tag/v7.20.0

On environments where the pnpm store is cached, doing a second pnpm
install solves the issue. These doesn't work in envs like Docker tho.

Could be fixed by adding a `main` field to the top-level package.json
as version v7.22.0 added a check for that.

See: https://github.com/pnpm/pnpm/releases/tag/v7.22.0
See: pnpm/pnpm#5868

But since we are not really publishing these packages we can just
remove the script.

[f:2h]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not running build script when installing via git
2 participants