pnpr@0.1.0-alpha.7
Breaking Changes📦 pnpmView on GitHub →
⚠ 1 breaking✨ 3 features🐛 1 fixes🔧 3 symbols
Summary
This release enhances pnpr by improving packument response headers and refining how client registry configurations and resolution modes are communicated to servers. It also fixes an issue with pnpm installs honoring specific settings.
⚠️ Breaking Changes
- The pnpr resolve and verify-lockfile request bodies have changed. Clients and servers must be on matching versions to ensure compatibility, as the protocol is still experimental and unversioned.
Migration Steps
- Ensure that both the pnpr server and its clients are updated to matching versions to maintain compatibility with the updated resolve and verify-lockfile request bodies.
✨ New Features
- Packument responses now include a `Last-Modified` header derived from `time.modified`, allowing clients to check package release age via `HEAD` probes instead of downloading full metadata.
- pnpr resolve requests now include the client's registry configuration (URL, scopes, bare-specifier prefixes, and `serverType`), enabling better routing of scoped dependencies to the correct registry.
- pnpr resolve requests now include the client's `resolutionMode`, ensuring that installs delegated to a pnpr server respect the client's version selection preferences (e.g., `time-based`, `lowest-direct`).
🐛 Bug Fixes
- Fixed `pnpm` installs using pnpr to correctly honor the client's `autoInstallPeers`, `dedupePeers`, and `excludeLinksFromLockfile` settings.