@_linked/cli 1.23.0 → 1.24.0
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 +15 -0
- package/README.md +1 -1
- package/package.json +3 -12
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.24.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- [#142](https://github.com/linked-fw/cli/pull/142) [`8a3734e`](https://github.com/linked-fw/cli/commit/8a3734e00eb8dcc0bea6ec502e7acaddbef927bd) Thanks [@flyon](https://github.com/flyon)! - Require `@_linked/core@^2.22.8` (was `^2.21.0`), and pin it in the lockfile.
|
|
8
|
+
|
|
9
|
+
The declared range was wide enough that the resolved core depended on whatever the
|
|
10
|
+
consumer — or this repo's own CI, via `package-lock.json` — happened to install. Core
|
|
11
|
+
decides how a shape's IRI is minted, so a stale core made this package emit legacy
|
|
12
|
+
`data.lincd.org` IRIs instead of the arch-02 `linked.cm` scheme. Which IRIs a published
|
|
13
|
+
package produces should not be a function of the installer's dependency tree.
|
|
14
|
+
|
|
15
|
+
Minor rather than patch: this raises the minimum core a consumer must resolve, so it
|
|
16
|
+
changes what gets installed rather than only what this package does internally.
|
|
17
|
+
|
|
3
18
|
## 1.23.0
|
|
4
19
|
|
|
5
20
|
### Minor Changes
|
package/README.md
CHANGED
|
@@ -265,7 +265,7 @@ Templates live in `defaults/`:
|
|
|
265
265
|
|
|
266
266
|
`linked create-app <name>` copies `defaults/app-with-backend/` to the new app's folder, substitutes `${name}` / `${hyphen_name}` / `${app_prefix}` / `${app_domain}` placeholders in selected files, and copies `linked.backend.datasets.example.json` → `linked.backend.datasets.json` so first boot works zero-config. Dependencies are installed with `npm install`, and the next-steps message tells you to run `npm start`.
|
|
267
267
|
|
|
268
|
-
|
|
268
|
+
### `linked create-app --template react-native`
|
|
269
269
|
|
|
270
270
|
`linked create-app <name> --template react-native` (with the usual `--app-name`, `--app-prefix`, `--app-domain`,
|
|
271
271
|
`--skip-install`) copies `defaults/app-react-native/` instead of cloning the web template. The result is an npm
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@_linked/cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.24.0",
|
|
4
4
|
"packageManager": "npm@11.19.1",
|
|
5
5
|
"description": "Command line tools for the @_linked/* packages and apps",
|
|
6
6
|
"main": "lib/esm/index.js",
|
|
@@ -40,15 +40,7 @@
|
|
|
40
40
|
"test:template": "RUN_TEMPLATE_FULL=1 jest --config jest.template.config.cjs",
|
|
41
41
|
"prettier": "prettier \"src/**/*.{js,jsx,ts,tsx,css,scss}\" --check",
|
|
42
42
|
"prettier:fix": "npm run prettier -- --write",
|
|
43
|
-
"format": "npm run prettier:fix
|
|
44
|
-
},
|
|
45
|
-
"lint-staged": {
|
|
46
|
-
"*.{js,ts,tsx}": [
|
|
47
|
-
"prettier --write"
|
|
48
|
-
],
|
|
49
|
-
"*.{scss,css}": [
|
|
50
|
-
"prettier --write"
|
|
51
|
-
]
|
|
43
|
+
"format": "npm run prettier:fix"
|
|
52
44
|
},
|
|
53
45
|
"keywords": [
|
|
54
46
|
"linked",
|
|
@@ -78,7 +70,7 @@
|
|
|
78
70
|
"LICENSE"
|
|
79
71
|
],
|
|
80
72
|
"dependencies": {
|
|
81
|
-
"@_linked/core": "^2.
|
|
73
|
+
"@_linked/core": "^2.22.8",
|
|
82
74
|
"@babel/core": "^7.24.0",
|
|
83
75
|
"@babel/plugin-proposal-decorators": "^7.24.0",
|
|
84
76
|
"@babel/plugin-transform-runtime": "^7.24.0",
|
|
@@ -148,6 +140,5 @@
|
|
|
148
140
|
"prettier": "^3.2.5",
|
|
149
141
|
"testcontainers": "^10.13.2"
|
|
150
142
|
},
|
|
151
|
-
"peerDepencencies": {},
|
|
152
143
|
"type": "module"
|
|
153
144
|
}
|