Skip to content

support new arch, Expo 53+ - #59

Open
song-react wants to merge 28 commits into
prisma:mainfrom
song-react:main
Open

song-react wants to merge 28 commits into
prisma:mainfrom
song-react:main

Conversation

@song-react

@song-react song-react commented Nov 23, 2025 •

Copy link
Copy Markdown

Summary by CodeRabbit

  • New Features

    • Added support for React Native's new architecture with automatic fallback to legacy architecture.
  • Bug Fixes

    • Enhanced initialization safety checks to prevent crashes from uninitialized components.
    • Improved simulator and device build compatibility.
  • Chores

    • Optimized migration bundling during the build process.
    • Improved memory management for internal callbacks.

@coderabbitai

coderabbitai Bot commented Mar 14, 2026 •

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

This PR adds a synchronous native Prisma execution entry point, updates JavaScript proxy routing and type contracts, patches the installed React Native runtime at install time, and changes platform-specific installation and header-resolution logic.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 20.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ❓ Inconclusive No pull request description was provided, so intent beyond the code changes can't be assessed. Add a short description summarizing the new-arch, Expo 53+, sync-query, and runtime patching changes.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the main change: new-architecture support and Expo 53+ compatibility.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d89adffc-66b7-4720-a069-b88a786e04fb

📥 Commits

Reviewing files that changed from the base of the PR and between 78fa48b and 28e3245.

📒 Files selected for processing (5)
  • android/src/main/java/com/prisma/PrismaModule.java
  • copy-migrations.sh
  • cpp/QueryEngineHostObject.h
  • cpp/react-native-prisma.cpp
  • ios/Prisma.mm

Comment thread android/src/main/java/com/prisma/PrismaModule.java Outdated
Comment thread copy-migrations.sh Outdated
Comment thread cpp/QueryEngineHostObject.h Outdated
Comment thread ios/Prisma.mm Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@cpp/react-native-prisma.cpp`:
- Around line 203-206: The query response path in the Prisma JSI bridge can
crash when prisma_query returns a null response without setting error_ptr.
Update the response handling in react-native-prisma.cpp near the code that
creates the JSI string to mirror the transaction handler null-response guard:
check response for null before calling jsi::String::createFromUtf8(rt,
response), and return a proper error/empty result path instead of converting a
null pointer.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1e65979e-48b5-4fa6-9ea0-49510fe14253

📥 Commits

Reviewing files that changed from the base of the PR and between 28e3245 and 1b01023.

📒 Files selected for processing (2)
  • cpp/react-native-prisma.cpp
  • src/index.ts

Comment thread cpp/react-native-prisma.cpp Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/patch-prisma-runtime.cjs`:
- Around line 19-22: The runtime patch in patch-prisma-runtime.cjs can end up
writing code that references __prismaReactNativeFastRead without having inserted
the helper first. Update the patch flow around the source.replace logic to
verify the marker/helper was actually injected before any later replacements or
writeFileSync output, and treat a missing "use strict"; match as an unsupported
runtime shape that should fail early instead of emitting a broken runtime.
- Around line 72-77: The postinstall patch in patchPrismaRuntime currently only
warns when the Prisma React Native runtime patch fails, which lets installation
continue with an unpatched runtime. Update the catch path in patchPrismaRuntime
to treat failures as non-recoverable: propagate the error, rethrow it, or set a
non-zero exit code after logging, so unsupported runtime shapes, permission
issues, and write failures cause installation to fail. Keep the existing error
context from the catch block, but ensure the failure is surfaced instead of
silently succeeding.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 78c68b34-b6f8-4f23-941a-6449eacd90a8

📥 Commits

Reviewing files that changed from the base of the PR and between 1b01023 and 13c2b0d.

📒 Files selected for processing (2)
  • package.json
  • scripts/patch-prisma-runtime.cjs

Comment thread scripts/patch-prisma-runtime.cjs Outdated
Comment on lines +19 to +22
source = source.replace(
'"use strict";',
`"use strict";var ${marker}=e=>{try{let t=e?.query?.arguments??{};if(t.distinct!=null)return!1;if(e?.action==="findUnique"||e?.action==="findFirst")return!0;return e?.action==="findMany"&&typeof t.take==="number"&&Number.isFinite(t.take)&&Math.abs(t.take)<=100}catch{return!1}};`
);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Verify the helper insertion before writing the patched runtime.

If "use strict"; is absent but the later string matches still succeed, Line 53 writes a runtime that calls an undefined __prismaReactNativeFastRead. Treat a missed helper insertion as an unsupported runtime shape.

Proposed fix
-  source = source.replace(
-    '"use strict";',
-    `"use strict";var ${marker}=e=>{try{let t=e?.query?.arguments??{};if(t.distinct!=null)return!1;if(e?.action==="findUnique"||e?.action==="findFirst")return!0;return e?.action==="findMany"&&typeof t.take==="number"&&Number.isFinite(t.take)&&Math.abs(t.take)<=100}catch{return!1}};`
-  );
+  const strictHeader = '"use strict";';
+  if (!source.includes(strictHeader)) {
+    throw new Error(
+      `Unsupported `@prisma/client` react-native strict header shape: ${runtimePath}`
+    );
+  }
+
+  source = source.replace(
+    strictHeader,
+    `${strictHeader}var ${marker}=e=>{try{let t=e?.query?.arguments??{};if(t.distinct!=null)return!1;if(e?.action==="findUnique"||e?.action==="findFirst")return!0;return e?.action==="findMany"&&typeof t.take==="number"&&Number.isFinite(t.take)&&Math.abs(t.take)<=100}catch{return!1}};`
+  );
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
source = source.replace(
'"use strict";',
`"use strict";var ${marker}=e=>{try{let t=e?.query?.arguments??{};if(t.distinct!=null)return!1;if(e?.action==="findUnique"||e?.action==="findFirst")return!0;return e?.action==="findMany"&&typeof t.take==="number"&&Number.isFinite(t.take)&&Math.abs(t.take)<=100}catch{return!1}};`
);
const strictHeader = '"use strict";';
if (!source.includes(strictHeader)) {
throw new Error(
`Unsupported `@prisma/client` react-native strict header shape: ${runtimePath}`
);
}
source = source.replace(
strictHeader,
`${strictHeader}var ${marker}=e=>{try{let t=e?.query?.arguments??{};if(t.distinct!=null)return!1;if(e?.action==="findUnique"||e?.action==="findFirst")return!0;return e?.action==="findMany"&&typeof t.take==="number"&&Number.isFinite(t.take)&&Math.abs(t.take)<=100}catch{return!1}};`
);
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/patch-prisma-runtime.cjs` around lines 19 - 22, The runtime patch in
patch-prisma-runtime.cjs can end up writing code that references
__prismaReactNativeFastRead without having inserted the helper first. Update the
patch flow around the source.replace logic to verify the marker/helper was
actually injected before any later replacements or writeFileSync output, and
treat a missing "use strict"; match as an unsupported runtime shape that should
fail early instead of emitting a broken runtime.

Comment thread scripts/patch-prisma-runtime.cjs Outdated
@song-react

Copy link
Copy Markdown
Author

Prisma 7 官方已经不再发布 React Native Rust Query Engine,方向改为“WASM Query Compiler + Driver Adapter”。所以正确升级不是重新编译旧 20MB 引擎,而是让你的 fork 变成轻量 JSI SQLite Driver Adapter;这样体积更小,同时底层 SQL 仍可同步直达 C++。

等待我的更新

song added 15 commits August 25, 2026 13:43
song and others added 8 commits October 4, 2026 20:47
- 使用 Nitro 同步桥连接原生 Query Compiler 与库内 SQLite3 执行器,移除 Expo Modules、expo-sqlite 和相关补丁依赖
- 由本包 postinstall 自动接入官方 prisma-client 生成器,默认无参连接 app.db,统一官方、本包与任意合法 output 的模型和 Client 入口
- 保留 BigInt 无损读写、设备迁移及同步 CRUD,复用官方结果扩展处理计算字段、select 与关联查询
- 精简依赖和生成配置,更新 README 为从 @prisma/client 导入的简短 Provider 示例
- 验证 Release/Hermes 模拟器 16 组运行场景、8 个合法输出与 5 个拒绝边界、重复安装和生成幂等
- 将默认和命名数据库恢复到 iOS Library 目录,保持原 React Native Prisma 的文件路径与无参 API
- 保留自定义目录能力,直接读取旧 app.db,由已有迁移机制升级记录结构并保留业务数据
- Release/Hermes 16 组验证通过,包括旧 Library 数据库、命名和自定义目录、BigInt、同步查询与结果扩展
- 使用 SQLite savepoint 兼容查询计划内部事务,保留完整同步模型与结果扩展
- 拒绝旧数组和异步回调,禁止事务结束后继续使用 tx
- 简化事务示例并说明默认沿用 Library/app.db
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant