feat(alpha): support-pnpm-package-manager [ZEND-6808] #2654
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelpineirocontentful
force-pushed
the
canary
branch
from
2c55b3c to
a5cc5c9
Compare
michaelpineirocontentful
force-pushed
the
feat-support-pnpm-package-manager
branch
from
79268d1 to
91ce91f
Compare
Based on [this PR](#2631) , with minor tweaks.
michaelpineirocontentful
force-pushed
the
feat-support-pnpm-package-manager
branch
from
91ce91f to
bde44f7
Compare
t-col
approved these changes
Aug 22, 2025
michaelpineirocontentful
restored the
feat-support-pnpm-package-manager
branch
michaelpineirocontentful
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is based on this one here, and adds a few changes - mostly around how we will detect the fallback package manager.
This PR adds support for the
--pnpmCLI option, and pnpm support in general, for thecreate-contentful-apptool. This PR does not convert the entire monorepo to use pnpm.Why is this needed?
For third party apps using pnpm as a package manage, trying to create Contentful apps with
create-contentful-appvia a custom npm script (or any kind of script, really) can end up erroring out when the new app's dependencies are installed because of how different local versions of pnpm and npm are handled.The commands given in console for installing dependencies, and for creating app definitions, are misleading in this case. There was also some ambiguity and unexpected behavior in the handling of when both
--yarnand--npmflags were passed, and npm would be preferred even if it wasn't the current package manager. With this change, multiple package manager flags are ignored and the currently active package manager will be used; this is the same behavior as omitting a package manager flag at all.This PR updates all areas that package managers are referenced, including the Segment.io analytics track call. Comprehensive test coverage is provided.