@forthtilliath/react-native-kit 0.7.0 → 0.7.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.
Files changed (2) hide show
  1. package/README.md +3 -1
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -30,7 +30,7 @@ import { ChangelogNotes } from "@forthtilliath/react-native-kit/ChangelogNotes";
30
30
 
31
31
  This is the recommended way to import: Metro (React Native's bundler) doesn't reliably tree-shake, so pulling from a single deep-import path keeps peer dependencies you don't use (`expo-image-picker`, `expo-speech-recognition`, `react-native-gesture-handler`...) out of your bundle entirely, rather than merely unused.
32
32
 
33
- A root barrel is also available for convenience when you don't mind that trade-off:
33
+ A root barrel is also available for convenience:
34
34
 
35
35
  ```ts
36
36
  import {
@@ -39,6 +39,8 @@ import {
39
39
  } from "@forthtilliath/react-native-kit";
40
40
  ```
41
41
 
42
+ **Avoid the barrel under Jest (or any other CommonJS `require` consumer).** `export * from` re-exports are evaluated eagerly on `require()` — unlike Metro's ESM bundling, there's no tree-shaking to skip the unused ones. Requiring the barrel from _any_ file, even one that only wants a framework-agnostic util like `getMostRecentIds`, pulls in every component's module graph, including native-module imports (`expo-speech-recognition` via `VoiceSearchButton`/`PickerModal`) that don't exist in a Jest environment — this throws `Cannot find native module '...'` at require time, not just at runtime for an unrendered component. Deep imports only ever load the one module you asked for, so they don't have this problem in any environment.
43
+
42
44
  ### `<ChangelogNotes notes={...} styles={...} />`
43
45
 
44
46
  Renders GitHub-style release notes — as produced by `@forthtilliath/expo-release-updates`'s `parseChangelogNotes` — as headings, bulleted items, and bold-aware text, instead of showing the raw Markdown syntax in a plain `Text`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forthtilliath/react-native-kit",
3
- "version": "0.7.0",
3
+ "version": "0.7.1",
4
4
  "type": "module",
5
5
  "license": "MIT",
6
6
  "publishConfig": {
@@ -44,8 +44,8 @@
44
44
  "react-test-renderer": "19.2.3",
45
45
  "typescript": "^5.9.3",
46
46
  "vitest": "^4.1.10",
47
- "@forthtilliath/typescript-config": "0.0.0",
48
- "@forthtilliath/eslint-config": "0.0.0"
47
+ "@forthtilliath/eslint-config": "0.0.0",
48
+ "@forthtilliath/typescript-config": "0.0.0"
49
49
  },
50
50
  "scripts": {
51
51
  "lint": "eslint . --max-warnings 0",