Add packageManager field to package.json #103
Open
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
mansona
reviewed
Oct 23, 2025
Fix condition syntax
This reverts commit 94c3ac3.
NullVoxPopuli
force-pushed
the
add-packageManager-to-package-json
branch
from
26051d4 to
477c225
Compare
Contributor
Author
|
I made: #105 Because I couldn't handle all the ejs anymore. ugh |
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.
I found out in testing: #101, that pnpm/action-setup now requires the pnpm version to be set.
It's unfortunate we can't use the packageManager field.
If we had an async hook in blueprint generation (at all), we could get the latest version of npm, pnpm, whatever, and set that.
This PR also makes me feel like we should split the workflow files by packageManager, because all the conditional logic is a nightmare in the current templated files/ci.yml