@_linked/cli 1.45.6 → 1.46.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.46.0
+
+### Minor Changes
+
+- [#250](https://github.com/linked-fw/cli/pull/250) [`293c265`](https://github.com/linked-fw/cli/commit/293c265b166a99ca5ebf3ed6d5cc966cd35ca4e0) Thanks [@flyon](https://github.com/flyon)! - `linked create-app --template react-native` now scaffolds an app on `@_linked/react` 2 and the framework releases built on it: `@_linked/react` 2.0.1 (was 1.6.4), `@_linked/schema` 1.5.0 (was 1.4.0), `@_linked/core` 2.28.1 (was 2.26.0; React 2 needs `^2.27.0`), `@_linked/server` 2.24.8, `@_linked/server-utils` 1.12.3, `@_linked/fuseki` 3.4.2, `@_linked/s3` 1.6.2 and `@_linked/cli` 1.45.6. The pins stay exact. `npm ls @_linked/react --all` in a new app shows only 2.0.1; before, `@_linked/primitives` 1.8.0 (through `@_linked/schema`) installed a second copy, 2.0.1, next to the app's 1.6.4.
+
+  A new app also has one React again. `@_linked/server` 2.24.5 and later take `react` and `react-dom` as peers, and npm resolved the peers of hoisted packages to the newest React (19.3.0) at the root, nesting the app's 19.2.3 under `apps/mobile`, so `npm run check:react` failed and `@_linked/react` loaded a different React from the app. The root `package.json` now pins `react` 19.2.3, `services/api` pins `react` next to its `react-dom`, and `apps/mobile` pins `react-dom` 19.2.3 (without it, `npm install` failed with `ERESOLVE`: `react-dom@19.3.0` wants `react@^19.3.0`).
+
+  With React 2, mounted components refetch after a mutation and identical queries share one request. The template's `nativeDefaults` test gives its loading and error cases a subject each, because the error case otherwise joined the loading case's request, which never settles. Existing apps are not changed.
+
+  Minor rather than patch: the CLI's commands do not change, but a newly generated app runs on a new major of `@_linked/react`, with its reactive refetching.
+
 ## 1.45.6
 
 ### Patch Changes

package/defaults/app-react-native/README.md

@@ -60,9 +60,12 @@ cd apps/mobile && npx expo export --platform ios --output-dir /tmp/export
 
 ## React Native specifics
 
-- **One React.** `npm ls react` lists extra React copies nested under `@_linked/server` and
-  `@_linked/server-utils`; the app never loads them, which `npm run check:react` verifies. Do not use
-  `--legacy-peer-deps`: it would hide a duplicate React.
+- **One React.** React is a peer of the `@_linked/*` packages, and npm resolves the peers of hoisted packages
+  at the repo root. Without a pin there, npm puts the newest React at the root and nests the app's 19.2.3
+  under `apps/mobile`, so `@_linked/react` and `react-native` would load a different React from the app.
+  The root `package.json` therefore pins `react` to the same version as `apps/mobile`, and every workspace
+  that depends on `@_linked/server` pins `react-dom` with it. `npm run check:react` verifies the result. Do
+  not use `--legacy-peer-deps`: it would hide a duplicate React.
 - **Workspaces are enumerated**, never globbed, so foreign repositories checked out under `packages/` are not
   adopted. `.gitignore` uses `packages/*` plus a negation per workspace package (`packages/` cannot be negated).
 - **Metro** (`apps/mobile/metro.config.js`) watches the workspace root and searches both `node_modules`

package/defaults/app-react-native/apps/mobile/__tests__/nativeDefaults.test.tsx

@@ -45,7 +45,7 @@ const flush = () => new Promise((resolve) => setTimeout(resolve, 0));
 describe('@_linked/react/native render defaults', () => {
   test('a loading component renders only React Native elements', async () => {
     mode = 'loading';
-    await render(<ExampleLabel of={{ id: 'urn:example:1' }} />);
+    await render(<ExampleLabel of={{ id: 'urn:example:loading' }} />);
 
     expect(lowercaseHostTypes(screen.toJSON() as any)).toEqual([]);
     expect(screen.getByTestId('linked-loader')).toBeTruthy();
@@ -53,7 +53,9 @@ describe('@_linked/react/native render defaults', () => {
 
   test('a failed component renders only React Native elements', async () => {
     mode = 'error';
-    await render(<ExampleLabel of={{ id: 'urn:example:1' }} />);
+    // A subject of its own: @_linked/react shares one request per query and subject, so reusing the loading
+    // test's subject would join its request, which never settles, and never reach the error state.
+    await render(<ExampleLabel of={{ id: 'urn:example:error' }} />);
     // Let the rejected query settle and the component re-render into its error state.
     await act(flush);
 

package/defaults/app-react-native/apps/mobile/package.json

@@ -11,15 +11,16 @@
     "test:integration": "jest -c jest.integration.config.js --runInBand"
   },
   "dependencies": {
-    "@_linked/core": "2.26.0",
-    "@_linked/react": "1.6.4",
-    "@_linked/schema": "1.4.0",
-    "@_linked/server": "2.24.0",
+    "@_linked/core": "2.28.1",
+    "@_linked/react": "2.0.1",
+    "@_linked/schema": "1.5.0",
+    "@_linked/server": "2.24.8",
     "app-shapes": "*",
     "expo": "57.0.25",
     "expo-constants": "57.0.19",
     "expo-dev-client": "57.0.19",
     "react": "19.2.3",
+    "react-dom": "19.2.3",
     "react-native": "0.86.3"
   },
   "devDependencies": {

package/defaults/app-react-native/apps/mobile/src/components/PersonOverview.tsx

@@ -1,7 +1,8 @@
 // Example PersonOverview — demonstrates @_linked/react's data binding:
 // linkedSetComponent for the list (auto-runs the query, injects results and
 // an injected _refresh); linkedComponent for each row (see PersonPreview).
-// After Person.create the form calls _refresh() to re-run the list query.
+// The list refetches by itself after Person.create; the form also calls the
+// list's _refresh() through context, to show how to re-run a query by hand.
 // A React Native port of the web app-template's example (linked-fw/app-template).
 //
 // `linkedSetComponent` checks LinkedStorage when this module loads, so storage is imported first.

package/defaults/app-react-native/apps/mobile/src/components/PersonPreview.tsx

@@ -1,8 +1,10 @@
 // Example PersonPreview — single-Person row. Demonstrates @_linked/react's
 // linkedComponent: the wrapper runs the per-row query and injects query
-// result keys + `source` + `_refresh` into the render function. _refresh
-// patches local query state for optimistic UI; on delete, the parent
-// list re-runs via the PersonListRefresh context.
+// result keys + `source` + `_refresh` into the render function. After a
+// mutation, every mounted component whose query can read the changed data
+// refetches by itself; _refresh patches the shared cached result first, for
+// optimistic UI, and on delete the PersonListRefresh context re-runs the list
+// explicitly.
 // A React Native port of the web app-template's example (linked-fw/app-template).
 // Storage is imported first, so the row's queries go to the API store however this module is reached.
 import '../shell/storage';

package/defaults/app-react-native/package.json

@@ -16,9 +16,12 @@
     "test": "npm test -w apps/mobile && npm test -w services/api",
     "test:integration": "npm run test:integration -w apps/mobile"
   },
+  "dependencies": {
+    "react": "19.2.3"
+  },
   "devDependencies": {
     "eslint": "9.39.5",
     "eslint-config-expo": "57.0.2",
-    "typescript-eslint": "8.70.1"
+    "typescript-eslint": "8.71.0"
   }
 }

package/defaults/app-react-native/packages/app-shapes/package.json

@@ -16,9 +16,9 @@
     "build": "linked build"
   },
   "dependencies": {
-    "@_linked/core": "2.26.0"
+    "@_linked/core": "2.28.1"
   },
   "devDependencies": {
-    "@_linked/cli": "1.40.0"
+    "@_linked/cli": "1.45.6"
   }
 }

package/defaults/app-react-native/scripts/check-react.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 // One React for the app: `react` resolved from apps/mobile, from the installed @_linked/react and from react-native
-// must be the same file. `npm ls react` is not used because @_linked/server and @_linked/server-utils nest their
-// own copies, which the app never loads.
+// must be the same file. It checks resolution rather than `npm ls react`, because what matters is the file each
+// of them loads: a second copy nested under apps/mobile (see the README) passes `npm ls` and still splits React.
 import { existsSync, readFileSync, realpathSync } from 'node:fs';
 import { createRequire } from 'node:module';
 import { dirname, join, resolve } from 'node:path';

package/defaults/app-react-native/services/api/README.md

@@ -39,9 +39,9 @@ that port is the one Docker Compose publishes for this repo's `fuseki` service.
 
 ## Dependencies
 
-`react-dom` is a direct dependency although the API renders no pages: `LinkedServer` imports `react-dom/server`
-at load time, and the root React is 19.2.3 (for `apps/mobile`), so `@_linked/server`'s own `react-dom` 18 is
-nested where Vite SSR cannot resolve it. Pinning `react-dom` 19.2.3 here hoists it next to the root React.
+`react` and `react-dom` are direct dependencies although the API renders no pages: `LinkedServer` imports
+`react-dom/server` at load time, and `@_linked/server` takes both as peers. They are pinned to the React that
+`apps/mobile` uses (19.2.3), so npm installs one copy of each at the root instead of the newest release.
 
 `linked start` finds the hoisted `app-shapes` workspace and runs in workspace mode: Vite loads `app-shapes` from
 `src` through its `development` export condition, while published packages such as `@_linked/core` and

package/defaults/app-react-native/services/api/package.json

@@ -14,18 +14,19 @@
     "test": "node --experimental-strip-types --no-warnings=ExperimentalWarning --test test/*.test.mjs"
   },
   "dependencies": {
-    "@_linked/core": "2.26.0",
-    "@_linked/fuseki": "3.4.0",
-    "@_linked/s3": "1.6.0",
-    "@_linked/schema": "1.4.0",
-    "@_linked/server": "2.24.0",
-    "@_linked/server-utils": "1.12.0",
+    "@_linked/core": "2.28.1",
+    "@_linked/fuseki": "3.4.2",
+    "@_linked/s3": "1.6.2",
+    "@_linked/schema": "1.5.0",
+    "@_linked/server": "2.24.8",
+    "@_linked/server-utils": "1.12.3",
     "app-shapes": "*",
+    "react": "19.2.3",
     "react-dom": "19.2.3"
   },
   "devDependencies": {
-    "@_linked/cli": "1.40.0",
-    "@types/node": "22.20.4",
+    "@_linked/cli": "1.45.6",
+    "@types/node": "22.20.5",
     "typescript": "6.0.3"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@_linked/cli",
-  "version": "1.45.6",
+  "version": "1.46.0",
   "packageManager": "npm@12.2.0",
   "description": "Command line tools for the @_linked/* packages and apps",
   "main": "lib/esm/index.js",
@@ -90,7 +90,7 @@
     "minimatch": "^9.0.4",
     "ora": "^8.0.1",
     "require-extensions": "^0.0.4",
-    "rimraf": "^5.0.7",
+    "rimraf": "^6.0.0",
     "semver": "^7.8.5",
     "staged-git-files": "^1.3.0",
     "tailwindcss": "^4.1.4",