@pnpm/store.pkg-finder 1100.0.37 → 1100.0.38

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @pnpm/store.pkg-finder
 
+## 1100.0.38
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fetching.directory-fetcher@1100.0.37
+  - @pnpm/store.cafs@1100.3.6
+
 ## 1100.0.37
 
 ### Patch Changes

package/lib/index.d.ts

@@ -12,19 +12,6 @@ export interface ReadPackageFileMapOptions {
  * Reads the file index for a package and returns a `Map<string, string>`
  * mapping filenames to absolute paths on disk.
  *
- * Picks the store key by resolution shape:
- * - Directory packages: fetches the file list from the local directory.
- * - Git-hosted tarballs (codeload.github.com / gitlab.com / bitbucket.org):
- *   keyed by `gitHostedStoreIndexKey(packageId, { built: true })`. The
- *   lockfile pins their integrity for security, but the cached payload
- *   depends on whether build scripts ran during fetch (preparePackage), so
- *   the `built` dimension is part of the key. Folding them under the
- *   integrity-only key would collapse that distinction.
- * - npm-registry tarballs and binary archives with integrity: keyed by
- *   `storeIndexKey(integrity, packageId)`.
- * - Other tarball / git resolutions without integrity: keyed by
- *   `gitHostedStoreIndexKey(packageId, { built: true })`.
- *
  * For CAFS packages, the content-addressed digests are resolved to file
  * paths upfront, so callers get a uniform map regardless of resolution type.
  *

package/lib/index.js

@@ -8,19 +8,6 @@ import { familySync } from 'detect-libc';
  * Reads the file index for a package and returns a `Map<string, string>`
  * mapping filenames to absolute paths on disk.
  *
- * Picks the store key by resolution shape:
- * - Directory packages: fetches the file list from the local directory.
- * - Git-hosted tarballs (codeload.github.com / gitlab.com / bitbucket.org):
- *   keyed by `gitHostedStoreIndexKey(packageId, { built: true })`. The
- *   lockfile pins their integrity for security, but the cached payload
- *   depends on whether build scripts ran during fetch (preparePackage), so
- *   the `built` dimension is part of the key. Folding them under the
- *   integrity-only key would collapse that distinction.
- * - npm-registry tarballs and binary archives with integrity: keyed by
- *   `storeIndexKey(integrity, packageId)`.
- * - Other tarball / git resolutions without integrity: keyed by
- *   `gitHostedStoreIndexKey(packageId, { built: true })`.
- *
  * For CAFS packages, the content-addressed digests are resolved to file
  * paths upfront, so callers get a uniform map regardless of resolution type.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/store.pkg-finder",
-  "version": "1100.0.37",
+  "version": "1100.0.38",
   "description": "Read a package's file map from the content-addressable store",
   "keywords": [
     "pnpm",
@@ -27,16 +27,16 @@
     "!*.map"
   ],
   "dependencies": {
-    "@pnpm/fetching.directory-fetcher": "1100.0.36",
+    "@pnpm/fetching.directory-fetcher": "1100.0.37",
     "@pnpm/resolving.resolver-base": "1101.3.2",
-    "@pnpm/store.cafs": "1100.3.5",
+    "@pnpm/store.cafs": "1100.3.6",
     "@pnpm/store.index": "1101.0.0",
     "@pnpm/types": "1102.1.1",
     "detect-libc": "^2.1.2"
   },
   "devDependencies": {
     "@jest/globals": "30.4.1",
-    "@pnpm/store.pkg-finder": "1100.0.37"
+    "@pnpm/store.pkg-finder": "1100.0.38"
   },
   "engines": {
     "node": ">=22.13"