Skip to content

Conversation

@NullVoxPopuli
Copy link
Contributor

@NullVoxPopuliNullVoxPopuli commented Oct 22, 2025

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

@NullVoxPopuliNullVoxPopuli added the bug Something isn't working label Oct 22, 2025
@NullVoxPopuliNullVoxPopuliforce-pushed the add-packageManager-to-package-json branch from 26051d4 to 477c225CompareOctober 25, 2025 17:46
@NullVoxPopuli
Copy link
ContributorAuthor

I made: #105

Because I couldn't handle all the ejs anymore. ugh

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugSomething isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@NullVoxPopuli@mansona@void-mAlex