@pnpm/store.pkg-finder 1100.0.24 → 1100.0.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,26 @@
1
1
  # @pnpm/store.pkg-finder
2
2
 
3
+ ## 1100.0.26
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies:
8
+ - @pnpm/fetching.directory-fetcher@1100.0.26
9
+ - @pnpm/resolving.resolver-base@1100.5.5
10
+ - @pnpm/store.cafs@1100.1.16
11
+
12
+ ## 1100.0.25
13
+
14
+ ### Patch Changes
15
+
16
+ - Republished every package: the tarballs published by the v11.13.1 through v11.16.0 releases were missing most of their compiled files due to a packing bug [#13164](https://github.com/pnpm/pnpm/issues/13164).
17
+
18
+ - Updated dependencies:
19
+ - @pnpm/fetching.directory-fetcher@1100.0.25
20
+ - @pnpm/resolving.resolver-base@1100.5.4
21
+ - @pnpm/store.cafs@1100.1.15
22
+ - @pnpm/store.index@1100.2.2
23
+
3
24
  ## 1100.0.24
4
25
 
5
26
  ### Patch Changes
package/lib/index.d.ts ADDED
@@ -0,0 +1,35 @@
1
+ import type { Resolution } from '@pnpm/resolving.resolver-base';
2
+ import { type StoreIndex } from '@pnpm/store.index';
3
+ export interface ReadPackageFileMapOptions {
4
+ storeDir: string;
5
+ storeIndex: StoreIndex;
6
+ lockfileDir: string;
7
+ virtualStoreDirMaxLength: number;
8
+ }
9
+ /**
10
+ * Reads the file index for a package and returns a `Map<string, string>`
11
+ * mapping filenames to absolute paths on disk.
12
+ *
13
+ * Picks the store key by resolution shape:
14
+ * - Directory packages: fetches the file list from the local directory.
15
+ * - Git-hosted tarballs (codeload.github.com / gitlab.com / bitbucket.org):
16
+ * keyed by `gitHostedStoreIndexKey(packageId, { built: true })`. The
17
+ * lockfile pins their integrity for security, but the cached payload
18
+ * depends on whether build scripts ran during fetch (preparePackage), so
19
+ * the `built` dimension is part of the key. Folding them under the
20
+ * integrity-only key would collapse that distinction.
21
+ * - npm-registry tarballs with integrity: keyed by
22
+ * `storeIndexKey(integrity, packageId)`.
23
+ * - Other tarball / git resolutions without integrity: keyed by
24
+ * `gitHostedStoreIndexKey(packageId, { built: true })`.
25
+ *
26
+ * For CAFS packages, the content-addressed digests are resolved to file
27
+ * paths upfront, so callers get a uniform map regardless of resolution type.
28
+ *
29
+ * Note: this function does not include files from side effects (post-install
30
+ * scripts). Use the raw `PackageFilesIndex` if you need side-effect files.
31
+ *
32
+ * Returns `undefined` if the resolution type is unsupported, letting callers
33
+ * decide how to handle this case. Throws if the index file cannot be read.
34
+ */
35
+ export declare function readPackageFileMap(packageResolution: Resolution, packageId: string, opts: ReadPackageFileMapOptions): Promise<Map<string, string> | undefined>;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pnpm/store.pkg-finder",
3
- "version": "1100.0.24",
3
+ "version": "1100.0.26",
4
4
  "description": "Read a package's file map from the content-addressable store",
5
5
  "keywords": [
6
6
  "pnpm",
@@ -27,14 +27,14 @@
27
27
  "!*.map"
28
28
  ],
29
29
  "dependencies": {
30
- "@pnpm/fetching.directory-fetcher": "1100.0.24",
31
- "@pnpm/resolving.resolver-base": "1100.5.3",
32
- "@pnpm/store.cafs": "1100.1.14",
33
- "@pnpm/store.index": "1100.2.1"
30
+ "@pnpm/fetching.directory-fetcher": "1100.0.26",
31
+ "@pnpm/resolving.resolver-base": "1100.5.5",
32
+ "@pnpm/store.cafs": "1100.1.16",
33
+ "@pnpm/store.index": "1100.2.2"
34
34
  },
35
35
  "devDependencies": {
36
36
  "@jest/globals": "30.4.1",
37
- "@pnpm/store.pkg-finder": "1100.0.24"
37
+ "@pnpm/store.pkg-finder": "1100.0.26"
38
38
  },
39
39
  "engines": {
40
40
  "node": ">=22.13"