Skip to content

Commit 17d8aee

Browse files
authored
docs: server config doc (#7092)
1 parent c21808e commit 17d8aee

File tree

8 files changed

+786
-4
lines changed

8 files changed

+786
-4
lines changed

packages/document/main-doc/docs/en/configure/app/usage.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Modern.js does not support configuring the same configuration item in both `pack
1313

1414
**Runtime configuration** can be configured in the `src/modern.runtime.(ts|js|mjs)` file.
1515

16-
**Server Runtime configuration** can be configured in the `modern.server-runtime.config.(ts|js|mjs)` file in the root path.
16+
**Server Runtime configuration** can be configured in the `server/modern.server.(ts|js|mjs)` file.
1717

1818
## Compile Configuration
1919

packages/document/main-doc/docs/en/guides/advanced-features/_meta.json

+1
Original file line numberDiff line numberDiff line change
@@ -23,5 +23,6 @@
2323
"label": "server-monitor",
2424
"collapsed": true
2525
},
26+
"custom-server",
2627
"web-server"
2728
]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,218 @@
1+
---
2+
sidebar_position: 16
3+
---
4+
5+
# Custom Server
6+
7+
Modern.js encapsulates most server-side capabilities required by projects, typically eliminating the need for server-side development. However, in certain scenarios such as user authentication, request preprocessing, or adding page skeletons, custom server-side logic may still be necessary.
8+
9+
## Custom Server Capabilities
10+
11+
Create the `server/modern.server.ts` file in the project directory, and you can add the following configurations to extend the Server:
12+
- **Middleware**
13+
- **Render Middleware**
14+
- **Server Plugin**
15+
16+
In the **Plugin**, you can define **Middleware** and **RenderMiddleware**. The middleware loading process is illustrated in the following diagram:
17+
18+
<img
19+
src="https://lf3-static.bytednsdoc.com/obj/eden-cn/10eh7nuhpenuhog/server-md-wf.png"
20+
style={{ width: '100%', maxWidth: '540px' }}
21+
/>
22+
23+
### Basic Configuration
24+
25+
```ts title="server/modern.server.ts"
26+
import { defineServerConfig } from '@modern-js/server-runtime';
27+
28+
export default defineServerConfig({
29+
middlewares: [],
30+
renderMiddlewares: [],
31+
plugins: [],
32+
});
33+
```
34+
35+
36+
### Type Definition
37+
38+
`defineServerConfig` type definition is as follows:
39+
40+
```ts
41+
import type { MiddlewareHandler } from 'hono';
42+
43+
type MiddlewareOrder = 'pre' | 'post' | 'default';
44+
type MiddlewareObj = {
45+
name: string;
46+
path?: string;
47+
method?: 'options' | 'get' | 'post' | 'put' | 'delete' | 'patch' | 'all';
48+
handler: MiddlewareHandler | MiddlewareHandler[];
49+
before?: Array<MiddlewareObj['name']>;
50+
order?: MiddlewareOrder;
51+
};
52+
type ServerConfig = {
53+
middlewares?: MiddlewareObj[];
54+
renderMiddlewares?: MiddlewareObj[];
55+
plugins?: (ServerPlugin | ServerPluginLegacy)[];
56+
}
57+
```
58+
59+
60+
### Middleware
61+
62+
Middleware supports executing custom logic before and after the **request handling** and **page routing** processes in Modern.js services.
63+
That is, if custom logic needs to handle both API routes and affect page routes, then Middleware is the obvious choice. If you only need to handle BFF API routes, this can be achieved by configuring the `path` to the BFF's `prefix`.
64+
65+
:::note
66+
In the BFF scenario, BFF routing will only go through Middleware when the [runtime framework](/guides/advanced-features/bff/frameworks.html) is Hono.
67+
:::
68+
69+
#### Using Posture
70+
71+
```ts title="server/modern.server.ts"
72+
import { defineServerConfig, type MiddlewareHandler } from '@modern-js/server-runtime';
73+
import { getMonitors } from '@modern-js/runtime';
74+
75+
export const handler: MiddlewareHandler = async (c, next) => {
76+
const monitors = getMonitors();
77+
const start = Date.now();
78+
79+
await next();
80+
81+
const end = Date.now();
82+
// Report Duration
83+
monitors.timing('request_timing', end - start);
84+
};
85+
86+
export default defineServerConfig({
87+
middlewares: [
88+
{
89+
name: 'request-timing',
90+
handler,
91+
},
92+
],
93+
});
94+
```
95+
96+
:::warning
97+
You must execute the `next` function to proceed with the subsequent Middleware.
98+
:::
99+
100+
101+
### RenderMiddleware
102+
103+
If you only need to handle the logic before and after page rendering, modern.js also provides rendering middleware.
104+
105+
#### Using Posture
106+
107+
```ts title="server/modern.server.ts"
108+
import { defineServerConfig, type MiddlewareHandler } from '@modern-js/server-runtime';
109+
110+
// Inject render performance metrics
111+
const renderTiming: MiddlewareHandler = async (c, next) => {
112+
const start = Date.now();
113+
114+
await next();
115+
116+
const end = Date.now();
117+
c.res.headers.set('server-timing', `render; dur=${end - start}`);
118+
};
119+
120+
// Modify the Response Body
121+
const modifyResBody: MiddlewareHandler = async (c, next) => {
122+
await next();
123+
124+
const { res } = c;
125+
const text = await res.text();
126+
const newText = text.replace('<body>', '<body> <h3>bytedance</h3>');
127+
128+
c.res = c.body(newText, {
129+
status: res.status,
130+
headers: res.headers,
131+
});
132+
};
133+
134+
export default defineServerConfig({
135+
renderMiddlewares: [
136+
{
137+
name: 'render-timing',
138+
handler: renderTiming,
139+
},
140+
{
141+
name: 'modify-res-body',
142+
handler: modifyResBody,
143+
},
144+
],
145+
});
146+
```
147+
148+
149+
### Plugin
150+
151+
Modern.js supports adding the aforementioned middleware and rendering middleware for the Server in custom plugins.
152+
153+
#### Using Posture
154+
155+
156+
```ts title="server/plugins/server.ts"
157+
import type { ServerPluginLegacy } from '@modern-js/server-runtime';
158+
159+
export default (): ServerPluginLegacy => ({
160+
name: 'serverPlugin',
161+
setup(api) {
162+
return {
163+
prepare(serverConfig) {
164+
const { middlewares, renderMiddlewares } = api.useAppContext();
165+
166+
// Inject server-side data for page dataLoader consumption
167+
middlewares?.push({
168+
name: 'server-plugin-middleware',
169+
handler: async (c, next) => {
170+
c.set('message', 'hi modern.js');
171+
await next();
172+
// ...
173+
},
174+
});
175+
176+
// redirect
177+
renderMiddlewares?.push({
178+
name: 'server-plugin-render-middleware',
179+
handler: async (c, next) => {
180+
const user = getUser(c.req);
181+
if (!user) {
182+
return c.redirect('/login');
183+
}
184+
185+
await next();
186+
},
187+
});
188+
return serverConfig;
189+
},
190+
};
191+
},
192+
});
193+
```
194+
195+
196+
```ts title="server/modern.server.ts"
197+
import { defineServerConfig } from '@modern-js/server-runtime';
198+
import serverPlugin from './plugins/serverPlugin';
199+
200+
export default defineServerConfig({
201+
plugins: [serverPlugin()],
202+
});
203+
```
204+
205+
206+
```ts title="src/routes/page.data.ts"
207+
import { useHonoContext } from '@modern-js/server-runtime';
208+
import { defer } from '@modern-js/runtime/router';
209+
210+
export default () => {
211+
const ctx = useHonoContext();
212+
// Consuming Data Injected by the Server-Side
213+
const message = ctx.get('message');
214+
215+
// ...
216+
};
217+
218+
```

0 commit comments

Comments
 (0)