Skip to content

Conversation

hokkyss
Copy link
Contributor

@hokkyss hokkyss commented Jul 28, 2025

Add docs for createIsomorphicFn, serverOnly, and clientOnly.

I am not quite sure whether "environment functions" is a good name though

Summary by CodeRabbit

  • Documentation
    • Added “Environment Functions” guide for React Start covering createIsomorphicFn, serverOnly, clientOnly, usage examples, runtime behavior, and tree-shaking notes.
    • Added Solid Start counterpart by mirroring/adapting React content.
    • Updated docs navigation to include “Environment Functions” under React and Solid.
    • Clarified React Server Functions doc by removing an outdated API Route warning and two call-source bullets.

@github-actions github-actions bot added the documentation Everything documentation related label Jul 28, 2025
@hokkyss hokkyss changed the title docs(start): environment functions docs docs(start): createIsomorphicFn and envOnly Jul 28, 2025
@hokkyss hokkyss force-pushed the main branch 3 times, most recently from a675dae to 9cab129 Compare July 29, 2025 01:52
### Complete Implementation

```tsx
const getEnv = createIsomorphicFn()
Copy link
Contributor

Choose a reason for hiding this comment

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

make those snippets complete by adding the import from '@tanstack/solid-start'

Copy link
Contributor

Choose a reason for hiding this comment

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

applies to all examples

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@@ -0,0 +1,3 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

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

once we have settled on the text for react, please duplicate and change the imports to point to solid

Copy link
Member

Choose a reason for hiding this comment

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

@hokkyss see the docs in docs/router/framework/solid/devtools.md which have a syntax for performing text replacements on the ref doc. So you shouldn't need to duplicate the entire document.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Understood. Updated guys. Thank you

@@ -98,7 +98,7 @@ response?: 'data' | 'full' | 'raw'
- From other server functions

> [!WARNING]
> Server functions cannot be called from API Routes. If you need to share business logic between server functions and API Routes, extract the shared logic into utility functions that can be imported by both.
Copy link
Contributor

Choose a reason for hiding this comment

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

i think we can now call server functions from API routes. please check and and if true, this text can be removed

Copy link
Member

Choose a reason for hiding this comment

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

@schiller-manuel is right. API routes as a whole became the new "Server Routes" which support calling Server Function.

This warning can be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Noted, this is deleted

@schiller-manuel
Copy link
Contributor

we also got those docs recently: b402bbc

maybe just improve those where needed?

@@ -98,7 +98,7 @@ response?: 'data' | 'full' | 'raw'
- From other server functions

> [!WARNING]
> Server functions cannot be called from API Routes. If you need to share business logic between server functions and API Routes, extract the shared logic into utility functions that can be imported by both.
Copy link
Member

Choose a reason for hiding this comment

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

@schiller-manuel is right. API routes as a whole became the new "Server Routes" which support calling Server Function.

This warning can be removed.

@@ -0,0 +1,3 @@
---
Copy link
Member

Choose a reason for hiding this comment

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

@hokkyss see the docs in docs/router/framework/solid/devtools.md which have a syntax for performing text replacements on the ref doc. So you shouldn't need to duplicate the entire document.

Use `createIsomorphicFn()` to define functions that behave differently depending on whether they are called on the client or the server. This is useful for safely sharing logic across environments while delegating environment-specific behavior to appropriate handlers.

> [!WARNING]
> Unimplemented function results in a no-op function.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe instead of a warning, this could be a small heading like "What is a no-op?", that'd show the user the type of a no-op.

Perhaps something like this:

type NoOpFunction = () => undefined // add a comment here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you!
I have added an explanation at the end of createIsomorphicFn as h4

@@ -122,6 +126,10 @@
"label": "Static Server Functions",
"to": "framework/solid/static-server-functions"
},
{
"label": "Environment Functions",
"to": "framework/react/environment-functions"
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"to": "framework/react/environment-functions"
"to": "framework/solid/environment-functions"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you! Updated.

@hokkyss hokkyss force-pushed the main branch 2 times, most recently from 9f6952d to f464374 Compare August 16, 2025 09:01
Copy link

coderabbitai bot commented Aug 16, 2025

Walkthrough

Adds React and Solid "Environment Functions" documentation and navigation entries; introduces a React doc describing createIsomorphicFn, serverOnly, and clientOnly; Solid's page references the React doc via YAML front matter; removes a warning and two bullets from the React server-functions doc.

Changes

Cohort / File(s) Summary of Changes
Docs navigation
docs/start/config.json
Added two nav entries for "Environment Functions" under React and Solid.
React docs
docs/start/framework/react/environment-functions.md, docs/start/framework/react/server-functions.md
Added new React doc describing environment-aware utilities (createIsomorphicFn, serverOnly, clientOnly) with examples and semantics; removed the API Route warning and two call-source bullets from the server-functions doc.
Solid docs
docs/start/framework/solid/environment-functions.md
Added YAML front matter referencing the React environment-functions doc with a replace mapping from reactsolid.

Sequence Diagram(s)

sequenceDiagram
  participant App as Application Code
  participant Iso as createIsomorphicFn
  participant Server as Server runtime
  participant Client as Client runtime

  Note over App,Iso: Define isomorphic function with .server() and .client()
  App->>Iso: invoke()
  alt Running on Server
    Iso->>Server: call server implementation
    Server-->>App: return server result
  else Running on Client
    Iso->>Client: call client implementation
    Client-->>App: return client result
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit scampers through each line,
Adding paths where docs align.
Server, client — neatly split,
Little hops make navigation fit.
🥕

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (11)
docs/start/config.json (1)

44-47: Optional: Consider renaming “Environment Functions” to “Isomorphic Utilities”

Since the PR description questions the naming, “Isomorphic Utilities” (or “Environment-aware Utilities”) may better convey the intent without implying only functions. If you prefer this, we should update both the page titles and these nav labels together.

Also applies to: 129-132

docs/start/framework/react/environment-functions.md (9)

10-15: Grammar: “Start provides”

Subject-verb agreement and light copy tweaks.

-Start provide three core environment functions:
+Start provides three core environment functions:

45-48: Grammar: “a no-op” and punctuation

Clarify the client behavior phrasing.

-// ℹ️ On the **client**, it is no-op (returns `undefined`)
+// ℹ️ On the **client**, it is a no-op (returns `undefined`).

59-62: Grammar: “a no-op” and punctuation

Same tweak for the server-side note.

-// ℹ️ On the **server**, it is no-op (returns `undefined`)
+// ℹ️ On the **server**, it is a no-op (returns `undefined`).

73-75: Grammar: “a no-op” and punctuation

Apply the same phrasing/punctuation for consistency.

-// ℹ️ On both **client** and **server**, it is no-op (returns `undefined`)
+// ℹ️ On both **client** and **server**, it is a no-op (returns `undefined`).

88-91: Fix heading: backticks and casing

Current “## envOnly Functions” renders oddly. Prefer plain language.

-## `env`Only Functions
+## Environment-only Functions

117-123: Tree-shaking section: wording and clarity

Minor grammar improvements and clearer phrasing.

-Environment functions are tree-shaken based on the environment for each bundle produced.
+Environment functions are tree-shaken per environment for each produced bundle.

-Functions created using `createIsomorphicFn()` are tree-shaken. All codes inside `.client()` are not included in server bundle, and vice-versa.
+Functions created using `createIsomorphicFn()` are tree-shaken. All code inside `.client()` is excluded from the server bundle, and vice versa.

-On the server, implementation of `clientOnly` functions are replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions on the client.
+In the server bundle, `clientOnly` implementations are replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions in the client bundle.

79-85: TS typing for no-op example

If we want to be explicit for TypeScript users, “void” is the idiomatic return type for a no-op (you can still note that it evaluates to undefined at runtime).

-// basic no-op implementation
-function noop() {}
+// basic no-op implementation (TypeScript)
+const noop: () => void = () => {}

99-112: Avoid locking docs to exact error message strings

The quoted error texts might diverge from implementation over time. Suggest describing the behavior generically or quoting less rigidly (e.g., “throws an error on the client/server”).

Would you like me to replace the exact strings with a generic description, or verify the current runtime messages in the codebase to keep them accurate?


1-4: Optional: Page title naming

If you decide to rename the nav label (e.g., to “Isomorphic Utilities”), mirror it here for consistency.

-title: Environment Functions
+title: Isomorphic Utilities
docs/start/framework/solid/environment-functions.md (1)

1-4: Consider adding a capitalized replacement and validate scope

If the source doc contains “React” (capitalized) or other proper nouns, also add a case-sensitive replacement to ensure titles and prose read naturally for Solid. Example:

 ---
 ref: docs/start/framework/react/environment-functions.md
-replace: { 'react': 'solid' }
+replace:
+  {
+    'react': 'solid',
+    'React': 'Solid'
+  }
 ---

Also, confirm the replacement mechanism applies to code blocks as intended (e.g., it should convert @tanstack/react-start to @tanstack/solid-start without affecting unrelated identifiers).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1ccf7c8 and f464374.

📒 Files selected for processing (4)
  • docs/start/config.json (2 hunks)
  • docs/start/framework/react/environment-functions.md (1 hunks)
  • docs/start/framework/react/server-functions.md (0 hunks)
  • docs/start/framework/solid/environment-functions.md (1 hunks)
💤 Files with no reviewable changes (1)
  • docs/start/framework/react/server-functions.md
🧰 Additional context used
🪛 LanguageTool
docs/start/framework/solid/environment-functions.md

[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ref: docs/start/framework/react/environment-functions.md replace: { 'react': 'solid' } ---

(QB_NEW_DE)

docs/start/framework/react/environment-functions.md

[grammar] ~12-~12: There might be a mistake here.
Context: ... to both client and server environments. - serverOnly: Ensures a function can only run on the...

(QB_NEW_EN)


[grammar] ~114-~114: There might be a mistake here.
Context: ...be called on the client!" ``` > [!NOTE] > These functions are useful for API acc...

(QB_NEW_EN)


[grammar] ~121-~121: There might be a mistake here.
Context: ...des inside .client() are not included in server bundle, and vice-versa. On the ...

(QB_NEW_EN)

🔇 Additional comments (3)
docs/start/config.json (2)

44-47: Nav entry for React looks good

The route slug matches the new doc file and placement (after Static Server Functions) is consistent.


129-132: Nav entry for Solid looks good

Slug matches the Solid doc and mirrors the React placement.

docs/start/framework/solid/environment-functions.md (1)

1-4: Front matter approach looks good

Using ref + replace keeps the content DRY across frameworks.

Copy link

nx-cloud bot commented Sep 3, 2025

View your CI Pipeline Execution ↗ for commit 8ac6f28

Command Status Duration Result
nx affected --targets=test:eslint,test:unit,tes... ✅ Succeeded <1s View ↗
nx run-many --target=build --exclude=examples/*... ✅ Succeeded 2s View ↗

☁️ Nx Cloud last updated this comment at 2025-09-03 03:33:46 UTC

Copy link

pkg-pr-new bot commented Sep 3, 2025

More templates

@tanstack/arktype-adapter

npm i https://pkg.pr.new/TanStack/router/@tanstack/arktype-adapter@4806

@tanstack/directive-functions-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/directive-functions-plugin@4806

@tanstack/eslint-plugin-router

npm i https://pkg.pr.new/TanStack/router/@tanstack/eslint-plugin-router@4806

@tanstack/history

npm i https://pkg.pr.new/TanStack/router/@tanstack/history@4806

@tanstack/react-router

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-router@4806

@tanstack/react-router-devtools

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-router-devtools@4806

@tanstack/react-router-ssr-query

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-router-ssr-query@4806

@tanstack/react-start

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-start@4806

@tanstack/react-start-client

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-start-client@4806

@tanstack/react-start-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-start-plugin@4806

@tanstack/react-start-server

npm i https://pkg.pr.new/TanStack/router/@tanstack/react-start-server@4806

@tanstack/router-cli

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-cli@4806

@tanstack/router-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-core@4806

@tanstack/router-devtools

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-devtools@4806

@tanstack/router-devtools-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-devtools-core@4806

@tanstack/router-generator

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-generator@4806

@tanstack/router-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-plugin@4806

@tanstack/router-ssr-query-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-ssr-query-core@4806

@tanstack/router-utils

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-utils@4806

@tanstack/router-vite-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/router-vite-plugin@4806

@tanstack/server-functions-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/server-functions-plugin@4806

@tanstack/solid-router

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-router@4806

@tanstack/solid-router-devtools

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-router-devtools@4806

@tanstack/solid-start

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-start@4806

@tanstack/solid-start-client

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-start-client@4806

@tanstack/solid-start-plugin

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-start-plugin@4806

@tanstack/solid-start-server

npm i https://pkg.pr.new/TanStack/router/@tanstack/solid-start-server@4806

@tanstack/start-client-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-client-core@4806

@tanstack/start-plugin-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-plugin-core@4806

@tanstack/start-server-core

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-server-core@4806

@tanstack/start-server-functions-client

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-server-functions-client@4806

@tanstack/start-server-functions-fetcher

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-server-functions-fetcher@4806

@tanstack/start-server-functions-server

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-server-functions-server@4806

@tanstack/start-storage-context

npm i https://pkg.pr.new/TanStack/router/@tanstack/start-storage-context@4806

@tanstack/valibot-adapter

npm i https://pkg.pr.new/TanStack/router/@tanstack/valibot-adapter@4806

@tanstack/virtual-file-routes

npm i https://pkg.pr.new/TanStack/router/@tanstack/virtual-file-routes@4806

@tanstack/zod-adapter

npm i https://pkg.pr.new/TanStack/router/@tanstack/zod-adapter@4806

commit: 8ac6f28

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

♻️ Duplicate comments (1)
docs/start/framework/solid/environment-functions.md (1)

1-4: Good use of ref/replace to avoid duplication.

The Solid doc correctly references the React doc and applies a replacement. This follows the prior guidance to avoid duplication.

🧹 Nitpick comments (10)
docs/start/framework/solid/environment-functions.md (1)

1-4: Broaden replace mapping to handle case and future-proof wording.

If the source doc ever uses "React" (capitalized), it won’t be replaced. Consider extending the mapping.

 ---
 ref: docs/start/framework/react/environment-functions.md
-replace: { 'react': 'solid' }
+replace: { 'react': 'solid', 'React': 'Solid' }
 ---

Please confirm the docs build system’s replace semantics are token-based (not substring-only) to avoid accidental replacements inside unrelated words.

docs/start/framework/react/environment-functions.md (9)

10-15: Grammar and clarity: subject-verb agreement and naming.

-Start provide three core environment functions:
+React Start provides three core environment functions:

36-48: Tighten “no-op” phrasing and punctuation.

-// ℹ️ On the **client**, it is no-op (returns `undefined`)
+// ℹ️ On the **client**, it's a no-op (returns `undefined`).

50-62: Mirror the “no-op” phrasing for consistency.

-// ℹ️ On the **server**, it is no-op (returns `undefined`)
+// ℹ️ On the **server**, it's a no-op (returns `undefined`).

64-76: Hyphenate compound modifier and add terminal punctuation.

-Here is an example of `createIsomorphicFn()` without any environment specific implementation:
+Here is an example of `createIsomorphicFn()` without any environment-specific implementation:
@@
-// ℹ️ On both **client** and **server**, it is no-op (returns `undefined`)
+// ℹ️ On both **client** and **server**, it's a no-op (returns `undefined`).

77-85: Type hint for no-op in TS.

In TS, an explicit void return improves clarity.

-// basic no-op implementation
-function noop() {}
+// basic no-op implementation
+const noop: () => void = () => {}

88-90: Rename section header for readability.

-## `env`Only Functions
+## Environment-only helpers

99-101: Avoid hard-coding exact error message text unless guaranteed stable.

Prefer generic wording to prevent drift if messages change.

-// ❌ On client: throws "serverOnly() functions can only be called on the server!"
+// ❌ On client: throws an Error.

If the exact message is stable and tested, feel free to keep it—otherwise consider the generic phrasing.


110-112: Mirror error-message guidance for clientOnly.

-// ❌ On server: throws "clientOnly() functions can only be called on the client!"
+// ❌ On server: throws an Error.

117-123: Tree-shaking copy edits and singular “code”.

-## Tree Shaking
+## Tree-shaking
@@
-Environment functions are tree-shaken based on the environment for each bundle produced.
+Environment functions are tree-shaken per environment for each bundle produced.
@@
-Functions created using `createIsomorphicFn()` are tree-shaken. All codes inside `.client()` are not included in server bundle, and vice-versa.
+Functions created using `createIsomorphicFn()` are tree-shaken. All code inside `.client()` is excluded from the server bundle, and vice versa.
@@
-On the server, implementation of `clientOnly` functions are replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions on the client.
+On the server, the implementation of `clientOnly` functions is replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions on the client.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f464374 and 8ac6f28.

📒 Files selected for processing (4)
  • docs/start/config.json (2 hunks)
  • docs/start/framework/react/environment-functions.md (1 hunks)
  • docs/start/framework/react/server-functions.md (0 hunks)
  • docs/start/framework/solid/environment-functions.md (1 hunks)
💤 Files with no reviewable changes (1)
  • docs/start/framework/react/server-functions.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/start/config.json
🧰 Additional context used
🪛 LanguageTool
docs/start/framework/react/environment-functions.md

[grammar] ~12-~12: There might be a mistake here.
Context: ... to both client and server environments. - serverOnly: Ensures a function can only run on the...

(QB_NEW_EN)


[grammar] ~114-~114: There might be a mistake here.
Context: ...be called on the client!" ``` > [!NOTE] > These functions are useful for API acc...

(QB_NEW_EN)


[grammar] ~121-~121: There might be a mistake here.
Context: ...des inside .client() are not included in server bundle, and vice-versa. On the ...

(QB_NEW_EN)

docs/start/framework/solid/environment-functions.md

[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ref: docs/start/framework/react/environment-functions.md replace: { 'react': 'solid' } ---

(QB_NEW_DE)

🔇 Additional comments (2)
docs/start/framework/react/environment-functions.md (2)

24-34: Examples look good.

Clear server/client behavior; code imports are present and consistent.


94-112: Great, focused examples for serverOnly/clientOnly.

Concise and accurate usage guidance.

Please confirm the import path and symbol names (createIsomorphicFn, serverOnly, clientOnly) match the published API in @tanstack/react-start.

@SeanCassiere SeanCassiere merged commit bc5e78f into TanStack:main Sep 3, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Everything documentation related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants