forked from angular/angular-cli
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsetup-middlewares-plugin.ts
More file actions
170 lines (152 loc) · 5.33 KB
/
setup-middlewares-plugin.ts
File metadata and controls
170 lines (152 loc) · 5.33 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
/**
* @license
* Copyright Google LLC All Rights Reserved.
*
* Use of this source code is governed by an MIT-style license that can be
* found in the LICENSE file at https://angular.dev/license
*/
import { IncomingMessage, ServerResponse } from 'node:http';
import type { Connect, Plugin } from 'vite';
import {
ComponentStyleRecord,
angularHtmlFallbackMiddleware,
createAngularAssetsMiddleware,
createAngularComponentMiddleware,
createAngularHeadersMiddleware,
createAngularIndexHtmlMiddleware,
createAngularSsrExternalMiddleware,
createAngularSsrInternalMiddleware,
createChromeDevtoolsMiddleware,
html403,
} from '../middlewares';
import { AngularMemoryOutputFiles, AngularOutputAssets } from '../utils';
export enum ServerSsrMode {
/**
* No SSR
*/
NoSsr,
/**
* Internal server-side rendering (SSR) is handled through the built-in middleware.
*
* In this mode, the SSR process is managed internally by the dev-server's middleware.
* The server automatically renders pages on the server without requiring external
* middleware or additional configuration from the developer.
*/
InternalSsrMiddleware,
/**
* External server-side rendering (SSR) is handled by a custom middleware defined in server.ts.
*
* This mode allows developers to define custom SSR behavior by providing a middleware in the
* `server.ts` file. It gives more flexibility for handling SSR, such as integrating with other
* frameworks or customizing the rendering pipeline.
*/
ExternalSsrMiddleware,
}
interface AngularSetupMiddlewaresPluginOptions {
outputFiles: AngularMemoryOutputFiles;
assets: AngularOutputAssets;
extensionMiddleware?: Connect.NextHandleFunction[];
indexHtmlTransformer?: (content: string) => Promise<string>;
componentStyles: Map<string, ComponentStyleRecord>;
templateUpdates: Map<string, string>;
ssrMode: ServerSsrMode;
resetComponentUpdates: () => void;
projectRoot: string;
allowedHosts: true | string[];
devHost: string;
}
async function createEncapsulateStyle(): Promise<
(style: Uint8Array, componentId: string) => string
> {
const { encapsulateStyle } = await import('@angular/compiler');
const decoder = new TextDecoder('utf-8');
return (style, componentId) => {
return encapsulateStyle(decoder.decode(style), componentId);
};
}
export function createAngularSetupMiddlewaresPlugin(
options: AngularSetupMiddlewaresPluginOptions,
): Plugin {
return {
name: 'vite:angular-setup-middlewares',
enforce: 'pre',
async configureServer(server) {
const {
indexHtmlTransformer,
outputFiles,
extensionMiddleware,
assets,
componentStyles,
templateUpdates,
ssrMode,
resetComponentUpdates,
} = options;
// Headers, assets and resources get handled first
server.middlewares.use(createAngularHeadersMiddleware(server));
server.middlewares.use(createAngularComponentMiddleware(server, templateUpdates));
server.middlewares.use(
createAngularAssetsMiddleware(
server,
assets,
outputFiles,
componentStyles,
await createEncapsulateStyle(),
),
);
server.middlewares.use(
createChromeDevtoolsMiddleware(server.config.cacheDir, options.projectRoot),
);
extensionMiddleware?.forEach((middleware) => server.middlewares.use(middleware));
// Returning a function, installs middleware after the main transform middleware but
// before the built-in HTML middleware
// eslint-disable-next-line @typescript-eslint/no-misused-promises
return async () => {
// Vite/Connect do not expose a typed stack, cast once to a precise structural type.
const entry = server.middlewares.stack.find(
({ handle }) =>
typeof handle === 'function' && handle.name.startsWith('hostValidationMiddleware'),
);
if (typeof entry?.handle === 'function') {
const originalHandle = entry.handle as Connect.NextHandleFunction;
entry.handle = function angularHostValidationMiddleware(
req: IncomingMessage,
res: ServerResponse,
next: (err?: unknown) => void,
) {
originalHandle(
req,
{
writeHead: (code) => {
res.writeHead(code, { 'content-type': 'text/html' });
},
end: () => {
const hostname = req.headers.host?.toLowerCase().split(':')[0] ?? '';
res.end(html403(hostname));
},
} as ServerResponse,
next,
);
};
}
if (ssrMode === ServerSsrMode.ExternalSsrMiddleware) {
server.middlewares.use(
await createAngularSsrExternalMiddleware(server, indexHtmlTransformer),
);
return;
}
if (ssrMode === ServerSsrMode.InternalSsrMiddleware) {
server.middlewares.use(createAngularSsrInternalMiddleware(server, indexHtmlTransformer));
}
server.middlewares.use(angularHtmlFallbackMiddleware);
server.middlewares.use(
createAngularIndexHtmlMiddleware(
server,
outputFiles,
resetComponentUpdates,
indexHtmlTransformer,
),
);
};
},
};
}