@couch-kit/devtools 3.0.0 → 3.0.2
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 +38 -0
- package/package.json +7 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,43 @@
|
|
|
1
1
|
# @couch-kit/devtools
|
|
2
2
|
|
|
3
|
+
## 3.0.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#151](https://github.com/faluciano/react-native-couch-kit/pull/151) [`ff839a6`](https://github.com/faluciano/react-native-couch-kit/commit/ff839a67c54aaf1f042b598d59d7918f03814c92) Thanks [@faluciano](https://github.com/faluciano)! - Fix an over-strict peer dependency that pinned devtools to one exact client
|
|
8
|
+
release.
|
|
9
|
+
|
|
10
|
+
The peer range was `workspace:*`, which publishing rewrites to the current
|
|
11
|
+
version — so `@couch-kit/devtools@3.0.0` demanded _exactly_
|
|
12
|
+
`@couch-kit/client@0.11.0`, and any client patch would conflict. devtools uses
|
|
13
|
+
one type-only import from client and nothing at runtime, so the peer is now a
|
|
14
|
+
wide, optional range (`>=0.9.0 <1.0.0`).
|
|
15
|
+
|
|
16
|
+
This also stops the runaway majors: because a peerDependency range change is
|
|
17
|
+
treated as breaking, every client release majored devtools — 0.2.10 → 1.0.0 →
|
|
18
|
+
2.0.0 → 3.0.0 in a day, each changelog reading "Patch Changes". Changesets is
|
|
19
|
+
now configured to bump peer dependents only when a release actually leaves
|
|
20
|
+
their range.
|
|
21
|
+
|
|
22
|
+
## 3.0.1
|
|
23
|
+
|
|
24
|
+
### Patch Changes
|
|
25
|
+
|
|
26
|
+
- [#149](https://github.com/faluciano/react-native-couch-kit/pull/149) [`182ef3d`](https://github.com/faluciano/react-native-couch-kit/commit/182ef3da3b5a2ec3ae242aa73fd4619d145eee43) Thanks [@faluciano](https://github.com/faluciano)! - Fix an over-strict peer dependency that pinned devtools to one exact client
|
|
27
|
+
release.
|
|
28
|
+
|
|
29
|
+
The peer range was `workspace:*`, which publishing rewrites to the current
|
|
30
|
+
version — so `@couch-kit/devtools@3.0.0` demanded _exactly_
|
|
31
|
+
`@couch-kit/client@0.11.0`, and any client patch would conflict. devtools uses
|
|
32
|
+
one type-only import from client and nothing at runtime, so the peer is now a
|
|
33
|
+
wide, optional range (`>=0.9.0 <1.0.0`).
|
|
34
|
+
|
|
35
|
+
This also stops the runaway majors: because a peerDependency range change is
|
|
36
|
+
treated as breaking, every client release majored devtools — 0.2.10 → 1.0.0 →
|
|
37
|
+
2.0.0 → 3.0.0 in a day, each changelog reading "Patch Changes". Changesets is
|
|
38
|
+
now configured to bump peer dependents only when a release actually leaves
|
|
39
|
+
their range.
|
|
40
|
+
|
|
3
41
|
## 3.0.0
|
|
4
42
|
|
|
5
43
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@couch-kit/devtools",
|
|
3
|
-
"version": "3.0.
|
|
3
|
+
"version": "3.0.2",
|
|
4
4
|
"description": "Developer tooling and debug overlay for Couch Kit games",
|
|
5
5
|
"main": "./dist/index.js",
|
|
6
6
|
"types": "./lib/index.d.ts",
|
|
@@ -39,7 +39,7 @@
|
|
|
39
39
|
"typescript": "^7.0.0"
|
|
40
40
|
},
|
|
41
41
|
"peerDependencies": {
|
|
42
|
-
"@couch-kit/client": "0.
|
|
42
|
+
"@couch-kit/client": ">=0.9.0 <1.0.0",
|
|
43
43
|
"react": ">=18.0.0"
|
|
44
44
|
},
|
|
45
45
|
"publishConfig": {
|
|
@@ -54,5 +54,10 @@
|
|
|
54
54
|
"type": "git",
|
|
55
55
|
"url": "https://github.com/faluciano/react-native-couch-kit.git",
|
|
56
56
|
"directory": "packages/devtools"
|
|
57
|
+
},
|
|
58
|
+
"peerDependenciesMeta": {
|
|
59
|
+
"@couch-kit/client": {
|
|
60
|
+
"optional": true
|
|
61
|
+
}
|
|
57
62
|
}
|
|
58
63
|
}
|