@dudousxd/nestjs-telescope-ui 1.23.0 → 1.23.1
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 +25 -0
- package/package.json +7 -7
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# @dudousxd/nestjs-telescope-ui
|
|
2
2
|
|
|
3
|
+
## 1.23.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [`80392f0`](https://github.com/DavideCarvalho/nestjs-telescope/commit/80392f0e4d038b50b5c8703275cfd91e3328064b) - Add NestJS 12 to the supported peer range.
|
|
8
|
+
|
|
9
|
+
NestJS 12.0.1 shipped the framework as pure ESM and raised its floor to Node >= 20.19. Telescope's
|
|
10
|
+
packages are already `"type": "module"`, so the ESM shift is a non-event here — nothing needed
|
|
11
|
+
porting, and every watcher, storage provider and dashboard route behaves identically on 11 and 12.
|
|
12
|
+
|
|
13
|
+
The declared peer ranges (`@nestjs/common`/`@nestjs/core` at `>=10.0.0`, `>=11.0.0` for the UI
|
|
14
|
+
package, and the satellite peers `@nestjs/bullmq`, `@nestjs/cache-manager`, `@nestjs/event-emitter`,
|
|
15
|
+
`@nestjs/schedule`) already admitted a 12.x resolution, so no range changed — what changed is that
|
|
16
|
+
the claim is now tested. Every package's dev and test matrix moved to the 12.x line, along with the
|
|
17
|
+
example app and the memory-soak harness, and the whole suite builds, typechecks and passes there.
|
|
18
|
+
|
|
19
|
+
Moving the example app and the soak harness matters for more than tidiness: leaving them on
|
|
20
|
+
`@nestjs/platform-express@11` left a second `@nestjs/platform-express` major in the workspace, and
|
|
21
|
+
pnpm's peer resolution then produced two distinct `@nestjs/core@12` instances. `tsc` correctly
|
|
22
|
+
rejected the resulting `ModuleRef` from one instance where the other was expected. That is a
|
|
23
|
+
workspace resolution artifact rather than a NestJS 12 incompatibility, but it is exactly the shape
|
|
24
|
+
of breakage a consumer sees when they upgrade half a dependency graph.
|
|
25
|
+
|
|
26
|
+
No behaviour change — peer ranges only affect what a package manager warns about on install.
|
|
27
|
+
|
|
3
28
|
## 1.23.0
|
|
4
29
|
|
|
5
30
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dudousxd/nestjs-telescope-ui",
|
|
3
|
-
"version": "1.23.
|
|
3
|
+
"version": "1.23.1",
|
|
4
4
|
"description": "Bundled dashboard + composable React components for @dudousxd/nestjs-telescope.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -54,7 +54,7 @@
|
|
|
54
54
|
"react-router-dom": "^6.0.0 || ^7.0.0",
|
|
55
55
|
"recharts": "^2.0.0 || ^3.0.0",
|
|
56
56
|
"reflect-metadata": "^0.1.13 || ^0.2.0",
|
|
57
|
-
"@dudousxd/nestjs-telescope": "^1.
|
|
57
|
+
"@dudousxd/nestjs-telescope": "^1.28.1"
|
|
58
58
|
},
|
|
59
59
|
"peerDependenciesMeta": {
|
|
60
60
|
"react": {
|
|
@@ -86,10 +86,10 @@
|
|
|
86
86
|
"tailwind-merge": "^2.6.0"
|
|
87
87
|
},
|
|
88
88
|
"devDependencies": {
|
|
89
|
-
"@nestjs/common": "^
|
|
90
|
-
"@nestjs/core": "^
|
|
91
|
-
"@nestjs/platform-express": "^
|
|
92
|
-
"@nestjs/testing": "^
|
|
89
|
+
"@nestjs/common": "^12.0.0",
|
|
90
|
+
"@nestjs/core": "^12.0.0",
|
|
91
|
+
"@nestjs/platform-express": "^12.0.0",
|
|
92
|
+
"@nestjs/testing": "^12.0.0",
|
|
93
93
|
"@tanstack/intent": "^0.3.2",
|
|
94
94
|
"@tanstack/react-query": "^5.0.0",
|
|
95
95
|
"@tanstack/react-table": "^9.0.0",
|
|
@@ -113,7 +113,7 @@
|
|
|
113
113
|
"typescript": "^5.4.0",
|
|
114
114
|
"vite": "^5.4.0",
|
|
115
115
|
"vitest": "^3.0.0",
|
|
116
|
-
"@dudousxd/nestjs-telescope": "1.
|
|
116
|
+
"@dudousxd/nestjs-telescope": "1.28.1"
|
|
117
117
|
},
|
|
118
118
|
"engines": {
|
|
119
119
|
"node": ">=20"
|