Add framework adapter#7847
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 78879dd
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview8 package(s) bumped directly, 5 bumped as dependents. 🟩 Patch bumps
|
Bundle Size BenchmarksThis pull request does not affect bundle size in any measured scenario. |
Merging this PR will degrade performance by 15.83%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Memory | mem server error-paths unmatched (react) |
264.5 KB | 808.2 KB | -67.27% |
| ❌ | Memory | mem server error-paths redirect (solid) |
441 KB | 553.9 KB | -20.38% |
| ❌ | Simulation | ssr not-found (react) |
59.3 ms | 65.2 ms | -9.12% |
| ❌ | Simulation | ssr control-flow unmatched 404 (vue) |
190 ms | 199.6 ms | -4.8% |
| ❌ | Memory | mem server peak-large-page (vue) |
711.6 KB | 745.1 KB | -4.49% |
| ❌ | Simulation | ssr not-found (solid) |
75.8 ms | 79.2 ms | -4.31% |
| ❌ | Simulation | client-async-pipeline navigation loop (react) |
49.8 ms | 51.8 ms | -3.74% |
| ❌ | Memory | mem server server-fn-churn (react) |
271.4 KB | 281.8 KB | -3.67% |
| ❌ | Simulation | ssr control-flow error 500 (react) |
62.3 ms | 64.6 ms | -3.54% |
| ❌ | Simulation | ssr control-flow route headers (react) |
61 ms | 63 ms | -3.21% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing taren/framework-adapter (68ad75a) with main (88f366a)
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud is proposing a fix for your failed CI:
We fixed three failing tasks introduced by the new framework adapter code. The rename fallback in generator.ts resolves EXDEV: cross-device link not permitted errors that occur when the generator's temp directory and the test's /tmp/ route directory reside on different filesystems, and the paths entries added to octane-start/tsconfig.json resolve the five TS2307 errors caused by TypeScript being unable to locate the unbuilt sub-path exports (/client, /server) during the type check.
Tip
✅ We verified this fix by re-running @tanstack/router-generator:test:unit, @tanstack/octane-start:test:types.
Suggested Fix changes
diff --git a/packages/octane-start/tsconfig.json b/packages/octane-start/tsconfig.json
index 23535530..e800b9a6 100644
--- a/packages/octane-start/tsconfig.json
+++ b/packages/octane-start/tsconfig.json
@@ -2,7 +2,11 @@
"extends": "../../tsconfig.json",
"compilerOptions": {
"module": "esnext",
- "types": ["node"]
+ "types": ["node"],
+ "paths": {
+ "@tanstack/octane-start/client": ["./src/client.ts"],
+ "@tanstack/octane-start/server": ["./src/server.ts"]
+ }
},
"include": ["src", "tests", "vite.config.ts", "vite.config.server-entry.ts"]
}
diff --git a/packages/router-generator/src/generator.ts b/packages/router-generator/src/generator.ts
index dc1ba405..3b357166 100644
--- a/packages/router-generator/src/generator.ts
+++ b/packages/router-generator/src/generator.ts
@@ -121,7 +121,23 @@ const DefaultFileSystem: fs = {
gid: Number(res.gid),
}
},
- rename: (oldPath, newPath) => fsp.rename(oldPath, newPath),
+ rename: async (oldPath, newPath) => {
+ try {
+ await fsp.rename(oldPath, newPath)
+ } catch (err) {
+ if (
+ typeof err === 'object' &&
+ err !== null &&
+ 'code' in err &&
+ (err as NodeJS.ErrnoException).code === 'EXDEV'
+ ) {
+ await fsp.copyFile(oldPath, newPath)
+ await fsp.unlink(oldPath)
+ } else {
+ throw err
+ }
+ }
+ },
writeFile: (filePath, content) => fsp.writeFile(filePath, content),
readFile: async (filePath: string) => {
try {
Or Apply changes locally with:
npx nx-cloud apply-locally 1osE-9Shl
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 Learn more about Self-Healing CI on nx.dev
|
we need to first merge #7830 |
The README referenced the prepared TanStack patch by a machine-local home path other maintainers cannot open. The patch now lives next to the package (packages/tanstack-start/tanstack-octane-native-injection.patch) and the README points at it, so the byte-identity claim is verifiable from any checkout: the patch applies clean on TanStack/router#7847's branch and reproduces the vendored renderRouterToStream.ts exactly (both re-verified). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ch (#176) * Sync the vendored stream file with the prepared upstream patch The native-injection renderRouterToStream was upstreamed as a ready-to-apply patch against TanStack/router#7847 (taren/framework-adapter @ 753f919e — the exact commit the vendor tree came from). Keep the vendored copy byte-identical to that patch (comment-only delta) so vendor-vs-upstream diffs stay clean, and document the one deliberate vendor divergence in the package README, which still claimed the whole tree was verbatim. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Commit the upstream patch into the repo (review feedback) The README referenced the prepared TanStack patch by a machine-local home path other maintainers cannot open. The patch now lives next to the package (packages/tanstack-start/tanstack-octane-native-injection.patch) and the README points at it, so the byte-identity claim is verifiable from any checkout: the patch applies clean on TanStack/router#7847's branch and reproduces the vendored renderRouterToStream.ts exactly (both re-verified). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
@trueadm — we audited your Octane Router and Start work against this branch and folded the TanStack-specific pieces into the official packages here, while leaving Octane’s renderer-agnostic meta-framework untouched. This PR now carries forward the Router/Start use cases we found: the Octane Router binding, The Query binding moved to the TanStack Query repo in TanStack/query#11101, with the original parity work plus sequential and nested custom-hook streaming SSR coverage. When you have time, could you review this PR and sign off that we preserved the valuable use cases and Octane-specific constraints from your implementation? Please call out anything you think was lost, changed materially, or should stay on the Octane side. |
trueadm
left a comment
trueadm
left a comment
There was a problem hiding this comment.
Nice stuff it all looks good to me. One thing though, you should probably align with Octane 0.1.13 before merging. The permanent-static and streamed ownership fixes in c36608cc were released in 0.1.13, so that should be the minimum tested version.
|
@trueadm Thanks — good catch. I pushed the Router/Start catalog and peer floors to make Octane 0.1.13 the minimum declared baseline in 3c46780. The repo's 24-hour minimumReleaseAge policy will not permit the 0.1.13 lockfile refresh until 2026-07-23 at 09:30 UTC, so I'll land that and the full 0.1.13 validation as soon as the gate clears, then post the results here. That will put the permanent-static and streamed-ownership fixes from c36608cc in our tested baseline without bypassing the supply-chain policy. |
You can likely have a local patch with the changes on top of 0.1.12 to validate and test first. That should enable you to give it a spin and confirm things work. If all is well then you can remove the patch tomorrow :) |
|
@trueadm The 0.1.13 alignment is complete and pushed. Both lockfiles were regenerated normally after the release-age gate cleared. Router/Start now resolves Octane 0.1.13 with That puts the permanent-static and streamed-ownership changes from |
3 participants
Summary
.tsrxroute generation, compiler transforms, code splitting, and HMRValidation
octanejs/octane@c36608ccminimumReleaseAge; resolves Octane 0.1.13 and@tsrx/core0.1.47