@appxdigital/appx-core 0.1.130 → 0.1.131
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 +23 -0
- package/README.md +1 -1
- package/package.json +4 -2
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,29 @@ This project follows the `MAJOR.MINOR.PATCH` scheme in `package.json`.
|
|
|
14
14
|
|
|
15
15
|
---
|
|
16
16
|
|
|
17
|
+
## [0.1.131] — 2026-10-19
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
|
|
21
|
+
- **`appx-core create` no longer requires npm 11.** New projects get `vitest ~4.0.18` and `unplugin-swc 1.5.10`: newer releases (vitest 4.1+ with vite 8, unplugin-swc 1.5.11+ with unplugin 3) bring peer graphs that npm 10 can't resolve (`Cannot read properties of null (reading 'edgesOut')` — an npm bug fixed only in npm 11.6). The created project no longer declares `engines.npm`.
|
|
22
|
+
|
|
23
|
+
### Fixed
|
|
24
|
+
|
|
25
|
+
- **A lockfile written by npm 10 now passes `npm ci` on npm 10.** npm 10 hoisted `ts-morph@16` (from `prisma-nestjs-graphql`) and `@opentelemetry/api@1.4.1` (from `prisma-case-format`) to the project root, where they don't satisfy the optional peer ranges of `@nestjs/graphql` (`ts-morph ^25`) and `vitest` (`@opentelemetry/api ^1.9`); its own `npm ci` then rejected the lockfile (`EUSAGE … does not satisfy`). The framework now depends on `ts-morph ^25.0.0` and `@opentelemetry/api ^1.9.0`, so those versions sit at the root and the older ones are nested — the layout npm 11 already produced. Projects declare nothing extra.
|
|
26
|
+
- CI runs `appx-core create` and `npm ci` of the created project on npm 10.
|
|
27
|
+
|
|
28
|
+
### Migration
|
|
29
|
+
|
|
30
|
+
Drop-in for the framework. For **existing projects whose CI uses npm 10**: if `npm ci` fails with `EBADPLATFORM` (`@esbuild/*`) or `Missing: … from lock file` and the project uses vitest, either run CI with npm 11 (`npm install -g npm@11` before `npm ci`), or hold the test tooling the same way and regenerate the lockfile:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
npm install -D vitest@~4.0.18 unplugin-swc@1.5.10
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Update the lockfile in place (preferably with npm 11) — **don't delete it**: a fresh resolution re-pulls today's versions, and on npm 10 can hit the same crash.
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
17
40
|
## [0.1.130] — 2026-10-18
|
|
18
41
|
|
|
19
42
|
Relations reached by a query now take part only through the related rows the caller can read — in filters, in nested selections at any depth, in `orderBy` and in `_count`.
|
package/README.md
CHANGED
|
@@ -112,7 +112,7 @@ AppX Core is designed as a **base layer** on top of NestJS:
|
|
|
112
112
|
|
|
113
113
|
### Prerequisites
|
|
114
114
|
|
|
115
|
-
- **Node.js 20+**
|
|
115
|
+
- **Node.js 20+**
|
|
116
116
|
- A running database (**MySQL** or **PostgreSQL** tested/validated)
|
|
117
117
|
|
|
118
118
|
### 1) Install the CLI
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@appxdigital/appx-core",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.131",
|
|
4
4
|
"description": "Appx Core is a library that provides a set of tools to help you build your application faster.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -31,7 +31,9 @@
|
|
|
31
31
|
},
|
|
32
32
|
"dependencies": {
|
|
33
33
|
"@adminjs/nestjs": "~7.0.0",
|
|
34
|
-
"
|
|
34
|
+
"@opentelemetry/api": "^1.9.0",
|
|
35
|
+
"express": "^5.1.0",
|
|
36
|
+
"ts-morph": "^25.0.0"
|
|
35
37
|
},
|
|
36
38
|
"devDependencies": {
|
|
37
39
|
"@nestjs/testing": "~11.0.0",
|