@pnpm/fetching.fetcher-base 1100.2.10 → 1100.2.12

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,24 @@
1
1
  # @pnpm/fetcher-base
2
2
 
3
+ ## 1100.2.12
4
+
5
+ ### Patch Changes
6
+
7
+ - `pnpm deploy` with a shared lockfile now copies workspace dependencies into the deploy directory, even when `packageImportMethod` is set to `hardlink`. Previously, their files were hard-linked to the workspace sources, so editing a source file also changed the deployed copy [pnpm/pnpm#12176](https://github.com/pnpm/pnpm/issues/12176).
8
+
9
+ - `pnpm install` no longer fails for an injected workspace dependency whose package publishes from a `publishConfig.directory` that its own `prepare` script builds. The injected copy now picks up that directory once `prepare` finishes building it. `pnpm install --frozen-lockfile` no longer reports the dependency as outdated while the directory has not been built yet. [pnpm/pnpm#7811](https://github.com/pnpm/pnpm/issues/7811)
10
+
11
+ - Updated dependencies:
12
+ - @pnpm/resolving.resolver-base@1101.3.2
13
+
14
+ ## 1100.2.11
15
+
16
+ ### Patch Changes
17
+
18
+ - Updated dependencies:
19
+ - @pnpm/resolving.resolver-base@1101.3.1
20
+ - @pnpm/types@1102.1.1
21
+
3
22
  ## 1100.2.10
4
23
 
5
24
  ### Patch Changes
package/lib/index.d.ts CHANGED
@@ -60,12 +60,23 @@ export interface DirectoryFetcherOptions {
60
60
  lockfileDir: string;
61
61
  readManifest?: boolean;
62
62
  }
63
+ export type LocalDirPackageImportMethod = 'hardlink' | 'clone-or-copy';
63
64
  export interface DirectoryFetcherResult {
64
65
  local: true;
65
66
  filesMap: FilesMap;
66
- packageImportMethod: 'hardlink';
67
+ packageImportMethod: LocalDirPackageImportMethod;
67
68
  manifest?: DependencyManifest;
68
69
  requiresBuild: boolean;
70
+ /**
71
+ * Whether the resolution's directory existed to walk. A project whose
72
+ * packed content is the output of its own `prepare` script (a
73
+ * `publishConfig.directory` built by `prepare`) has no source directory on
74
+ * a fresh install, so `false` here comes with an empty `filesMap` that
75
+ * does not mean the source is genuinely empty. Importers must not treat
76
+ * that as a reason to force a reimport that would overwrite an
77
+ * already-materialized copy.
78
+ */
79
+ sourceExists: boolean;
69
80
  }
70
81
  export type DirectoryFetcher = FetchFunction<DirectoryResolution, DirectoryFetcherOptions, DirectoryFetcherResult>;
71
82
  export interface Fetchers {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pnpm/fetching.fetcher-base",
3
- "version": "1100.2.10",
3
+ "version": "1100.2.12",
4
4
  "description": "Types for pnpm-compatible fetchers",
5
5
  "keywords": [
6
6
  "pnpm",
@@ -28,13 +28,13 @@
28
28
  "!*.map"
29
29
  ],
30
30
  "dependencies": {
31
- "@pnpm/resolving.resolver-base": "1101.3.0",
32
- "@pnpm/types": "1102.1.0",
31
+ "@pnpm/resolving.resolver-base": "1101.3.2",
32
+ "@pnpm/types": "1102.1.1",
33
33
  "@types/ssri": "^7.1.5"
34
34
  },
35
35
  "devDependencies": {
36
- "@pnpm/fetching.fetcher-base": "1100.2.10",
37
- "@pnpm/store.cafs-types": "1100.1.0"
36
+ "@pnpm/fetching.fetcher-base": "1100.2.12",
37
+ "@pnpm/store.cafs-types": "1100.1.1"
38
38
  },
39
39
  "engines": {
40
40
  "node": ">=22.13"