@jaypie/mcp 0.8.85 → 0.8.86
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.
|
@@ -9,7 +9,7 @@ import { gt } from 'semver';
|
|
|
9
9
|
/**
|
|
10
10
|
* Docs Suite - Documentation services (skill, version, release_notes)
|
|
11
11
|
*/
|
|
12
|
-
const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.
|
|
12
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.86#e508c355"
|
|
13
13
|
;
|
|
14
14
|
const __filename$1 = fileURLToPath(import.meta.url);
|
|
15
15
|
const __dirname$1 = path.dirname(__filename$1);
|
package/package.json
CHANGED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.6.5
|
|
3
|
+
date: 2026-06-28
|
|
4
|
+
summary: Raise @jaypie/errors peer floor to ^1.2.3 so ConflictError resolves
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Fixes
|
|
8
|
+
|
|
9
|
+
- Raise the `@jaypie/errors` peer dependency from a floorless `*` to `^1.2.3`.
|
|
10
|
+
- `0.6.4` imports `ConflictError`, which `@jaypie/errors` only began exporting in
|
|
11
|
+
`1.2.3`. The `*` peer was satisfied by an already-deduped older `@jaypie/errors`
|
|
12
|
+
(e.g. `1.2.1`), so esbuild and other bundlers failed with
|
|
13
|
+
`No matching export ... for import "ConflictError"` (and the runtime equivalent
|
|
14
|
+
`errors.ConflictError is not a constructor`).
|
|
15
|
+
- With the floor in place, installs resolve an `@jaypie/errors` that exports
|
|
16
|
+
`ConflictError` and bundling succeeds.
|
|
17
|
+
|
|
18
|
+
No runtime behavior changes.
|