pnpr@0.1.0-alpha.8
📦 pnpmView on GitHub →
✨ 5 features🐛 1 fixes🔧 4 symbols
Summary
Introduced an opt-in feature for reusing dependency build artifacts across machines via pnpr and enhanced registry revision handling for patches and package extensions.
Migration Steps
- Configure the new `remoteSideEffectsCache` setting to enable the opt-in proof of concept for reusing dependency build output.
- Specify the eligible `organization` and `packages` in the workspace configuration for the `remoteSideEffectsCache`.
- Manage signing-related configurations (`publish`, `keyId`, `builderId`, `trustedKeys`, `privateKey`) and provenance fields from the global config file or environment, as they are refused in `pnpm-workspace.yaml` when using `remoteSideEffectsCache`.
✨ New Features
- Added an opt-in proof of concept for reusing dependency build output across machines using signed, organization-scoped artifacts published and restored through pnpr.
- Hosted pnpr registries now serve newly published original artifacts from registry-scoped SHA-512 digest URLs.
- Allowed `pnpm update --patches` to refresh registry revisions through a configured pnpr server while retaining locked package versions.
- Added explicit registry revision selection with `<version>+rN` and `pnpm update --patches` for refreshing revision artifacts without changing package versions.
- Added support for registry replacement tarballs using standard integrity values, explicit revision fields, registry routing from the `registries` setting, non-redirecting integrity-addressed URLs, canonical safe-integer revision numbers, and pnpr proxying for immutable upstream revision artifacts.
🐛 Bug Fixes
- Forward `patchedDependencies` hashes and `packageExtensions` to pnpr so server-side resolution preserves patches and package extensions in the lockfile and installed packages.