Skip to content

Commit bd98d7d

Browse files
docs: remote function cannot be server-only modules (#14813)
* docs: remote function cannot be server-only modules * Update documentation/docs/20-core-concepts/60-remote-functions.md --------- Co-authored-by: Simon H <[email protected]>
1 parent 53b1b73 commit bd98d7d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

documentation/docs/20-core-concepts/60-remote-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ export default config;
3333

3434
## Overview
3535

36-
Remote functions are exported from a `.remote.js` or `.remote.ts` file, and come in four flavours: `query`, `form`, `command` and `prerender`. On the client, the exported functions are transformed to `fetch` wrappers that invoke their counterparts on the server via a generated HTTP endpoint. Remote files must be placed in your `src` directory.
36+
Remote functions are exported from a `.remote.js` or `.remote.ts` file, and come in four flavours: `query`, `form`, `command` and `prerender`. On the client, the exported functions are transformed to `fetch` wrappers that invoke their counterparts on the server via a generated HTTP endpoint. Remote files can be placed anywhere in your `src` directory (except inside the `src/lib/server` directory), and third party libraries can provide them, too.
3737

3838
## query
3939

0 commit comments

Comments
 (0)