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: only build git-hosted dependency if it has no main file #5868

Merged
merged 2 commits into from
Jan 3, 2023

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented Jan 2, 2023

close #5845

@zkochan zkochan requested a review from a team January 3, 2023 01:48
@zkochan zkochan merged commit 40a4818 into main Jan 3, 2023
@zkochan zkochan deleted the fix-git-prepare branch January 3, 2023 12:38
@zkochan zkochan added this to the v7.22 milestone Jan 4, 2023
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.

pnpm install fails with  ERR_PNPM_PREPARE_PKG_FAILURE
2 participants