@pnpm/lockfile.types 1100.0.2 → 1100.0.4

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.
Files changed (2) hide show
  1. package/lib/index.d.ts +13 -0
  2. package/package.json +3 -3
package/lib/index.d.ts CHANGED
@@ -80,6 +80,19 @@ export interface TarballResolution {
80
80
  tarball: string;
81
81
  integrity?: string;
82
82
  path?: string;
83
+ /**
84
+ * True for tarballs sourced from a git host (codeload.github.com /
85
+ * gitlab.com / bitbucket.org). Such tarballs need preparation
86
+ * (preparePackage / packlist) on extraction, and their cached content
87
+ * depends on whether build scripts ran, so they're addressed by
88
+ * gitHostedStoreIndexKey rather than the integrity-based key.
89
+ *
90
+ * The git resolver sets this when it produces the resolution; the
91
+ * lockfile loader sets it on entries whose URL matches a known git host
92
+ * for backward compatibility with lockfiles written before this field
93
+ * existed.
94
+ */
95
+ gitHosted?: boolean;
83
96
  }
84
97
  /**
85
98
  * directory on a file system
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pnpm/lockfile.types",
3
- "version": "1100.0.2",
3
+ "version": "1100.0.4",
4
4
  "description": "Types for the pnpm-lock.yaml lockfile",
5
5
  "keywords": [
6
6
  "pnpm",
@@ -26,12 +26,12 @@
26
26
  "!*.map"
27
27
  ],
28
28
  "dependencies": {
29
- "@pnpm/resolving.resolver-base": "1100.1.0",
30
29
  "@pnpm/patching.types": "1100.0.0",
30
+ "@pnpm/resolving.resolver-base": "1100.1.2",
31
31
  "@pnpm/types": "1101.0.0"
32
32
  },
33
33
  "devDependencies": {
34
- "@pnpm/lockfile.types": "1100.0.2"
34
+ "@pnpm/lockfile.types": "1100.0.4"
35
35
  },
36
36
  "engines": {
37
37
  "node": ">=22.13"