@react-navigation/lynx 0.4.0-canary-20260910-b29e3a12 → 0.4.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.
Files changed (2) hide show
  1. package/README.md +14 -0
  2. package/package.json +8 -2
package/README.md CHANGED
@@ -29,6 +29,20 @@ resolve: {
29
29
  },
30
30
  ```
31
31
 
32
+ `@react-navigation/core` also lists `react` as a peer dependency, which the
33
+ alias above satisfies at build time but no package manager can see. pnpm's
34
+ default `auto-install-peers` papers over that; with `strict-peer-dependencies`
35
+ on, tell pnpm the peer is intentionally absent:
36
+
37
+ ```yaml
38
+ # pnpm-workspace.yaml
39
+ peerDependencyRules:
40
+ ignoreMissing: ['react']
41
+ ```
42
+
43
+ The types are written against `@types/react` 19, so a TypeScript app needs
44
+ `@types/react@>=19.2` (declared as an optional peer).
45
+
32
46
  ## Usage
33
47
 
34
48
  ```tsx
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@react-navigation/lynx",
3
- "version": "0.4.0-canary-20260910-b29e3a12",
3
+ "version": "0.4.0",
4
4
  "description": "Lynx integration for React Navigation",
5
5
  "keywords": [
6
6
  "react",
@@ -37,7 +37,8 @@
37
37
  },
38
38
  "peerDependencies": {
39
39
  "@lynx-js/react": "*",
40
- "lynx-screens": "*"
40
+ "lynx-screens": "*",
41
+ "@types/react": ">=19.2"
41
42
  },
42
43
  "devDependencies": {
43
44
  "@lynx-js/react": "^0.126.0",
@@ -49,6 +50,11 @@
49
50
  "vitest": "^3.2.0",
50
51
  "lynx-screens": "0.1.0"
51
52
  },
53
+ "peerDependenciesMeta": {
54
+ "@types/react": {
55
+ "optional": true
56
+ }
57
+ },
52
58
  "scripts": {
53
59
  "typecheck": "tsc --noEmit",
54
60
  "test": "vitest run"