@pnpm/catalogs.resolver 1100.0.0 → 1100.1.0

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 ADDED
@@ -0,0 +1,13 @@
1
+ # @pnpm/catalogs.resolver
2
+
3
+ ## 1100.1.0
4
+
5
+ ### Minor Changes
6
+
7
+ - Catalogs can now resolve workspace dependencies through the `workspace:` protocol.
8
+
9
+ ## 1100.0.1
10
+
11
+ ### Patch Changes
12
+
13
+ - 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).
@@ -20,21 +20,7 @@ export function resolveFromCatalog(catalogs, wantedDependency) {
20
20
  error: new PnpmError('CATALOG_ENTRY_INVALID_RECURSIVE_DEFINITION', `Found invalid catalog entry using the catalog protocol recursively. The entry for '${wantedDependency.alias}' in catalog '${catalogName}' is invalid.`),
21
21
  };
22
22
  }
23
- // Ban catalog entries that use the workspace protocol for a few reasons:
24
- //
25
- // 1. It's kind of silly. It'd be better to encourage users to use the
26
- // workspace protocol directly.
27
- // 2. Catalogs cache the resolved version of a dependency specifier in
28
- // pnpm-lock.yaml for more consistent resolution across importers. The
29
- // link: resolutions can't be shared between importers.
30
23
  const protocolOfLookup = catalogLookup.split(':')[0];
31
- if (protocolOfLookup === 'workspace') {
32
- return {
33
- type: 'misconfiguration',
34
- catalogName,
35
- error: new PnpmError('CATALOG_ENTRY_INVALID_WORKSPACE_SPEC', `The workspace protocol cannot be used as a catalog value. The entry for '${wantedDependency.alias}' in catalog '${catalogName}' is invalid.`),
36
- };
37
- }
38
24
  // A future version of pnpm will try to support this. These protocols aren't
39
25
  // supported today since these are often relative file paths that users expect
40
26
  // to be relative to the repo root rather than the location of the pnpm
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pnpm/catalogs.resolver",
3
- "version": "1100.0.0",
3
+ "version": "1100.1.0",
4
4
  "description": "Dereferences catalog protocol specifiers into usable specifiers.",
5
5
  "keywords": [
6
6
  "pnpm",
@@ -9,8 +9,11 @@
9
9
  ],
10
10
  "license": "MIT",
11
11
  "funding": "https://opencollective.com/pnpm",
12
- "repository": "https://github.com/pnpm/pnpm/tree/main/catalogs/resolver",
13
- "homepage": "https://github.com/pnpm/pnpm/tree/main/catalogs/resolver#readme",
12
+ "repository": {
13
+ "type": "git",
14
+ "url": "https://github.com/pnpm/pnpm/tree/main/pnpm11/catalogs/resolver"
15
+ },
16
+ "homepage": "https://github.com/pnpm/pnpm/tree/main/pnpm11/catalogs/resolver#readme",
14
17
  "bugs": {
15
18
  "url": "https://github.com/pnpm/pnpm/issues"
16
19
  },
@@ -25,13 +28,13 @@
25
28
  "!*.map"
26
29
  ],
27
30
  "dependencies": {
28
- "@pnpm/catalogs.protocol-parser": "^1100.0.0",
29
- "@pnpm/error": "^1100.0.0"
31
+ "@pnpm/catalogs.protocol-parser": "^1100.0.1",
32
+ "@pnpm/error": "^1100.1.4"
30
33
  },
31
34
  "devDependencies": {
32
- "@jest/globals": "30.3.0",
33
- "@pnpm/catalogs.resolver": "1100.0.0",
34
- "@pnpm/catalogs.types": "1100.0.0"
35
+ "@jest/globals": "30.4.1",
36
+ "@pnpm/catalogs.resolver": "1100.1.0",
37
+ "@pnpm/catalogs.types": "1100.0.1"
35
38
  },
36
39
  "engines": {
37
40
  "node": ">=22.13"