docs(start): add imports and no-op explanation

Author: hokkyss

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

@@ -19,12 +19,11 @@ Start provide three core environment functions:
 
 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.
-
 ### Complete Implementation
 
 ```tsx
+import { createIsomorphicFn } from '@tanstack/react-start';
+
 const getEnv = createIsomorphicFn()
   .server(() => 'server')
   .client(() => 'client')
@@ -39,6 +38,8 @@ const env = getEnv()
 Here is an example of `createIsomorphicFn()` with only server implementation:
 
 ```tsx
+import { createIsomorphicFn } from '@tanstack/react-start';
+
 const serverImplementationOnly = createIsomorphicFn().server(() => 'server')
 
 const server = serverImplementationOnly()
@@ -51,6 +52,8 @@ const server = serverImplementationOnly()
 Here is an example of `createIsomorphicFn()` with only client implementation:
 
 ```tsx
+import { createIsomorphicFn } from '@tanstack/react-start';
+
 const clientImplementationOnly = createIsomorphicFn().client(() => 'client')
 
 const client = clientImplementationOnly()
@@ -63,12 +66,23 @@ const client = clientImplementationOnly()
 Here is an example of `createIsomorphicFn()` without any environment specific implementation:
 
 ```tsx
+import { createIsomorphicFn } from '@tanstack/react-start';
+
 const noImplementation = createIsomorphicFn()
 
 const noop = noImplementation()
 // ℹ️ On both **client** and **server**, it is no-op (returns `undefined`)
 ```
 
+#### What is a no-op?
+
+A no-op (short for "no operation") is a function that does nothing when executed - it simply returns `undefined` without performing any operations.
+
+```tsx
+// basic no-op implementation
+function noop() {}
+```
+
 ---
 
 ## `env`Only Functions
@@ -78,6 +92,8 @@ The `serverOnly` and `clientOnly` helpers enforce strict environment-bound execu
 ### `serverOnly`
 
 ```tsx
+import { serverOnly } from '@tanstack/react-start';
+
 const foo = serverOnly(() => 'bar')
 
 foo() // ✅ On server: returns "bar"
@@ -87,6 +103,8 @@ foo() // ✅ On server: returns "bar"
 ### `clientOnly`
 
 ```tsx
+import { clientOnly } from '@tanstack/react-start';
+
 const foo = clientOnly(() => 'bar')
 
 foo() // ✅ On client: returns "bar"
@@ -100,6 +118,7 @@ foo() // ✅ On client: returns "bar"
 
 Environment functions are tree-shaken based on the environment for each bundle produced.
 
-On the server, functions created using `createIsomorphicFn()` are tree-shaken. So, all code used inside `.client()` are not included in server bundle, and vice-versa.
+Functions created using `createIsomorphicFn()` are tree-shaken. All codes inside `.client()` are not included in 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.
+

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

@@ -97,9 +97,6 @@ response?: 'data' | 'full' | 'raw'
 - From client-side code
 - 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. See [Environment Functions](../environment-functions.md) for more.
-
 ## Accepting Parameters
 
 Server functions accept a single parameter, which can be a variety of types:

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

@@ -1,3 +1,4 @@
 ---
 ref: docs/start/framework/react/environment-functions.md
+replace: { 'react': 'solid' }
 ---