chore: migrate package management to npm#184
Merged
Merged
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
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.
Summary
pnpm-lock.yamlto npm lockfile v3 without changing direct dependency versionsoverridesnpm cifor reproducible clean installsWhy
Fulling is currently a single-package application and does not rely on pnpm-specific workspace features. Using the package manager bundled with Node.js removes the Corepack and pnpm bootstrap from contributor machines, CI, and container builds while retaining deterministic installs through
npm ci.Runtime and dependency upgrades are intentionally excluded and tracked separately in #183.
Validation
npm ci --ignore-scriptson Node.js 22.12 / npm 10npm run lintnpm test— 35 tests passednpm run test:e2e— 18 tests passednpm run buildCloses #180