@_linked/cli 1.4.0 → 1.4.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
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.4.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#24](https://github.com/linked-cm/cli/pull/24) [`c5d1321`](https://github.com/linked-cm/cli/commit/c5d13216bde74e591111a281253afcaf43c8bfb9) Thanks [@flyon](https://github.com/flyon)! - Template (`app-with-backend`) dep bumps so a fresh scaffold installs versions that match the APIs the template uses:
|
|
8
|
+
- `@_linked/core: ^2.6` (needs `parseDatasetsConfig` + `loadStores`)
|
|
9
|
+
- `@_linked/server: ^2.0` (needs the new `BackendAPIStore` config-object constructor + the dataset-terminology renames)
|
|
10
|
+
- `@_linked/server-utils: ^1.0.5` (1.0.4 shipped an empty tarball)
|
|
11
|
+
- `@_linked/react: ^1.3` (needs the loader/errorElement resolution chain + `_refresh` on `linkedSetComponent`)
|
|
12
|
+
- `@_linked/cli: ^1.4` (template uses the loader bin)
|
|
13
|
+
|
|
14
|
+
Also: `theme.css` top-comment no longer references the colours as "CN-branded" — they're just the default palette; users override `--color-primary-*` / `--color-secondary-*` to brand. README workspace-note generalized to "another repo's `packages/`" instead of a specific path.
|
|
15
|
+
|
|
3
16
|
## 1.4.0
|
|
4
17
|
|
|
5
18
|
### Minor Changes
|
|
@@ -36,20 +36,20 @@
|
|
|
36
36
|
"web3"
|
|
37
37
|
],
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"@_linked/core": "^2.
|
|
39
|
+
"@_linked/core": "^2.6",
|
|
40
40
|
"@_linked/auth": "~1.0",
|
|
41
|
-
"@_linked/server": "
|
|
42
|
-
"@_linked/server-utils": "
|
|
41
|
+
"@_linked/server": "^2.0",
|
|
42
|
+
"@_linked/server-utils": "^1.0.5",
|
|
43
43
|
"@_linked/schema": "^1.0",
|
|
44
44
|
"@_linked/fuseki": "^1.0",
|
|
45
|
-
"@_linked/react": "^1.
|
|
45
|
+
"@_linked/react": "^1.3",
|
|
46
46
|
"react": "^18.2",
|
|
47
47
|
"react-dom": "^18.2",
|
|
48
48
|
"react-error-boundary": "^3.1.3",
|
|
49
49
|
"react-router-dom": "^6.3.0"
|
|
50
50
|
},
|
|
51
51
|
"devDependencies": {
|
|
52
|
-
"@_linked/cli": "^1.
|
|
52
|
+
"@_linked/cli": "^1.4",
|
|
53
53
|
"@types/node": "^20.12.7",
|
|
54
54
|
"@types/react": "^18.0.17",
|
|
55
55
|
"@types/react-dom": "^18.0.6",
|
|
@@ -49,7 +49,7 @@ yarn start
|
|
|
49
49
|
|
|
50
50
|
The home page demonstrates the `@_linked` query DSL with a small Person CRUD — see `src/components/PersonOverview.tsx` and `src/components/PersonPreview.tsx`.
|
|
51
51
|
|
|
52
|
-
> If you scaffolded this app **inside an existing Yarn-workspace monorepo** (e.g. `
|
|
52
|
+
> If you scaffolded this app **inside an existing Yarn-workspace monorepo** (e.g. `packages/` of another repo), use `yarn install` — `npm install` walks up to the workspace root and may hit peer-dep conflicts there. Outside a workspace, either tool works.
|
|
53
53
|
|
|
54
54
|
## Storage
|
|
55
55
|
|
package/lib/cjs/package.json
CHANGED
package/lib/esm/package.json
CHANGED