Skip to content

fix: define packageManager field#7715

Merged
martinjagodic merged 1 commit intomainfrom
fix/define-package-manager
Feb 9, 2026
Merged

fix: define packageManager field#7715
martinjagodic merged 1 commit intomainfrom
fix/define-package-manager

Conversation

@yanthomasdev
Copy link
Contributor

Summary

Basically, this adds the packageManager field to avoid dependencies being installed using yarn or pnpm. The way they hoist and symlink packages all have differences, and if you installed the project using something else than npm (in my case, pnpm) it would lead to an issue when trying to run npm run build.

This is to improve the developer experience especially for first-time contributors, since many expect every repository to work fine nowadays with pnpm, for example. In a follow-up PR, we can definitely change to pnpm as default since it has better monorepo support than npm.

Test plan

If you try to run yarn install or pnpm install it will be blocked through corepack, e.g.
image

Checklist

Please add a x inside each checkbox:

A picture of a cute animal (not mandatory but encouraged)
image

@yanthomasdev yanthomasdev requested a review from a team as a code owner February 6, 2026 17:22
@github-actions github-actions bot added the type: bug code to address defects in shipped code label Feb 6, 2026
@martinjagodic martinjagodic merged commit a3a181e into main Feb 9, 2026
11 checks passed
@martinjagodic martinjagodic deleted the fix/define-package-manager branch February 9, 2026 08:23
martinjagodic pushed a commit to poslovnimediji/decap-cms that referenced this pull request Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug code to address defects in shipped code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants