@web-ts-toolkit/express-runtime 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright Junmin Ahn
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,337 @@
1
+ # `@web-ts-toolkit/express-runtime`
2
+
3
+ Express app factory plus serverless handler and local dev server helpers. Build
4
+ one Express app, run it as a serverless function **or** a local dev server with
5
+ minimal wiring changes. A CLI binary runs any Express app locally from a module
6
+ path.
7
+
8
+ ## Installation
9
+
10
+ ```sh
11
+ pnpm add @web-ts-toolkit/express-runtime express
12
+ ```
13
+
14
+ ## Highlights
15
+
16
+ - `createExpressApp()` — Express factory with pluggable lifecycle slots
17
+ (`preMiddleware`, `middleware`, `routers`, `postMiddleware`, `finalize`,
18
+ `errorHandler`), hardening defaults, and per-logger injection.
19
+ - `createServerlessHandler()` — wraps an Express app as a platform-agnostic
20
+ serverless handler (Netlify, Vercel, AWS Lambda) with a Buffer-body
21
+ workaround for serverless-http issue #305, a memoized `init` hook for cold
22
+ starts, and a `reset()` escape hatch for failed cold starts.
23
+ - `startLocalServer()` — `http.createServer` + `listen` with friendly
24
+ `EADDRINUSE` / `EACCES` errors, optional graceful `SIGINT` / `SIGTERM`
25
+ shutdown that drains in-flight requests, and a configurable timeout.
26
+ - CLI binary with three subcommands:
27
+ - `dev` — run an Express app as a local dev server
28
+ - `build` — bundle the app as a serverless handler using `tsup`
29
+ - `start` — smoke-test the bundled handler locally by translating HTTP ↔ serverless events
30
+
31
+ ## Quick Start
32
+
33
+ Choose **one** of the two runmodes per app instance. Calling both
34
+ `createServerlessHandler(app, …)` and `startLocalServer(app, …)` against the
35
+ same app instance mutates shared state (port setting, serverless-http wrapper)
36
+ — keep them separate.
37
+
38
+ ### Module API — serverless
39
+
40
+ ```ts
41
+ import { createExpressApp, createServerlessHandler } from '@web-ts-toolkit/express-runtime';
42
+ import { myRouter } from './routes';
43
+
44
+ // Derive the mount path from the environment so the same app serves both
45
+ // serverless (/.netlify/functions/main) and local (/api) URLs.
46
+ const baseUrl = () => (process.env.NODE_ENV === 'production' ? '/.netlify/functions/main' : '/api');
47
+
48
+ const app = createExpressApp({
49
+ routers: [{ path: baseUrl, handler: myRouter }],
50
+ errorHandler: (err, _req, res, _next) => {
51
+ res.status(500).json({ success: false, message: (err as Error).message });
52
+ },
53
+ });
54
+
55
+ export const handler = createServerlessHandler(app, {
56
+ init: async () => {
57
+ // cold-start hook: DB connections, cache warmup, etc.
58
+ },
59
+ });
60
+ ```
61
+
62
+ ### Module API — local dev server
63
+
64
+ ```ts
65
+ import { createExpressApp, startLocalServer } from '@web-ts-toolkit/express-runtime';
66
+ import { myRouter } from './routes';
67
+
68
+ const app = createExpressApp({
69
+ routers: [{ path: () => '/api', handler: myRouter }],
70
+ });
71
+
72
+ startLocalServer(app, {
73
+ port: 8080,
74
+ host: '0.0.0.0',
75
+ onShutdown: async () => {
76
+ // graceful cleanup (close DB, flush buffers, ...)
77
+ },
78
+ });
79
+ ```
80
+
81
+ ### CLI — dev (local server)
82
+
83
+ The `web-ts-toolkit-express-runtime dev` command runs any module that
84
+ default-exports an Express app (or an async function returning one) as a local
85
+ dev server:
86
+
87
+ ```sh
88
+ npx web-ts-toolkit-express-runtime dev ./dist/app.js --port 3000 --host localhost
89
+ ```
90
+
91
+ ```ts
92
+ // src/app.ts (precompile to dist/app.js, or run via tsx — see below)
93
+ import { createExpressApp } from '@web-ts-toolkit/express-runtime';
94
+
95
+ export default createExpressApp({
96
+ routers: [{ path: () => '/api', handler: myRouter }],
97
+ });
98
+ ```
99
+
100
+ For TypeScript app modules, run the CLI through `tsx`:
101
+
102
+ ```sh
103
+ npx tsx ./node_modules/@web-ts-toolkit/express-runtime/dist/cli.js dev ./src/app.ts
104
+ ```
105
+
106
+ > The `dev` command evaluates arbitrary code from `<app-module>` in the current
107
+ > process and inherits its privileges. Init logic (e.g. DB connections) should
108
+ > be placed at the top level of your app module since `dev` does not expose an
109
+ > `init` hook.
110
+
111
+ ### CLI — build (serverless bundle)
112
+
113
+ The `build` command generates a temporary serverless entry that wraps the app
114
+ with `createServerlessHandler`, then bundles it with `tsup` into a
115
+ deployment-ready file:
116
+
117
+ ```sh
118
+ npx web-ts-toolkit-express-runtime build ./src/app.ts --out-dir netlify/functions
119
+ ```
120
+
121
+ With an optional init hook (DB connections, cache warmup, etc.):
122
+
123
+ ```sh
124
+ npx web-ts-toolkit-express-runtime build ./src/app.ts --init ./src/init.ts --out-dir netlify/functions
125
+ ```
126
+
127
+ ```ts
128
+ // src/init.ts
129
+ export default async () => {
130
+ await mongoose.connect(process.env.MONGODB_URI);
131
+ };
132
+ ```
133
+
134
+ This produces `netlify/functions/handler.js` (configurable via `--out-name`)
135
+ that exports a `handler` function compatible with Netlify, Vercel, AWS Lambda,
136
+ and any platform that calls `(event, context)`.
137
+
138
+ > `tsup` is required for `build`: `pnpm add -D tsup`. `express` is always
139
+ > external; additional externals can be added via `--external`.
140
+
141
+ ### CLI — start (run a bundled handler locally)
142
+
143
+ The `start` command runs a bundled serverless handler locally by translating
144
+ HTTP requests into serverless events and the handler's results back into HTTP
145
+ responses — letting you smoke-test the exact `build` output without a
146
+ serverless platform:
147
+
148
+ ```sh
149
+ npx web-ts-toolkit-express-runtime build ./src/app.ts --out-dir dist
150
+ npx web-ts-toolkit-express-runtime start ./dist/handler.js --port 9000
151
+ ```
152
+
153
+ The handler module must export a `handler` function (named or default) that
154
+ accepts `(event, context)` and returns a result with `statusCode`, `headers`,
155
+ and `body` — the same shape produced by `createServerlessHandler` via
156
+ `serverless-http`.
157
+
158
+ > The adapter passes the raw request body as a Buffer (no body parsing) so the
159
+ > handler's request hook, including the serverless-http #305 workaround, runs
160
+ > identically to production.
161
+
162
+ ## Module API
163
+
164
+ ### `createExpressApp(options?): Express`
165
+
166
+ Creates and returns a configured Express application. Middleware is applied in
167
+ the following lifecycle order:
168
+
169
+ 1. `preMiddleware` _(logging, helmet, request-id)_
170
+ 2. body parsers (`express.json`, `express.urlencoded`)
171
+ 3. `middleware` _(cookies, sessions, auth, CORS)_
172
+ 4. `routers` and `router`
173
+ 5. `postMiddleware` _(404 catch-all)_
174
+ 6. `finalize` _(routes that should be wrapped by `errorHandler`)_
175
+ 7. `errorHandler`
176
+
177
+ Built-in hardening: `x-powered-by` is disabled, `etag` is off. `trust proxy`
178
+ defaults to **`false`** — opt in explicitly when behind a trusted upstream
179
+ proxy (otherwise `X-Forwarded-*` headers can be spoofed).
180
+
181
+ | Option | Type | Default | Description |
182
+ | ------------------ | ----------------------------------------- | ----------------------------------- | ------------------------------------------------ |
183
+ | `preMiddleware` | `RequestHandler[]` | `[]` | Registered before body parsers |
184
+ | `middleware` | `RequestHandler[]` | `[]` | Registered after body parsers, before routers |
185
+ | `postMiddleware` | `RequestHandler[]` | `[]` | Registered after all routers |
186
+ | `json` | `JsonOptions \| false` | `{ limit: '1mb' }` | `express.json()` options; `false` disables |
187
+ | `urlencoded` | `UrlEncodedOptions \| false` | `{ extended: false, limit: '1mb' }` | `express.urlencoded()` options; `false` disables |
188
+ | `router` | `RouterMount` | — | Single router convenience |
189
+ | `routers` | `RouterMount[]` | — | Multiple routers mounted in order |
190
+ | `trustProxy` | `boolean \| number \| string \| string[]` | `false` | Express `trust proxy` setting |
191
+ | `disablePoweredBy` | `boolean` | `true` | Disable `x-powered-by` header |
192
+ | `etag` | `boolean \| string` | `false` | Express `etag` setting |
193
+ | `finalize` | `(app) => void` | — | Hook to add routes that `errorHandler` catches |
194
+ | `errorHandler` | `ErrorRequestHandler` | — | Error handler registered last |
195
+ | `logger` | `Logger` | `console` | Logger used internally |
196
+
197
+ #### `RouterMount`
198
+
199
+ | Field | Type | Description |
200
+ | --------- | ------------------------ | ---------------------------------------------------------------------------------- |
201
+ | `path` | `string \| () => string` | Mount path or function returning one (lets the mount path derive from runtime env) |
202
+ | `handler` | `RequestHandler` | Router or middleware mounted at `path` |
203
+
204
+ ### `createServerlessHandler(app, options?): ServerlessHandler`
205
+
206
+ Wraps an Express app into a platform-agnostic serverless handler. Works with
207
+ Netlify, Vercel, AWS Lambda, and any platform that calls `(event, context)`.
208
+
209
+ Returns a handler function with an attached `reset()` method to retry a failed
210
+ cold-start (`init()` rejections are memoized alongside successes).
211
+
212
+ | Option | Type | Default | Description |
213
+ | ------------------- | ------------------------------------------------------- | ---------------------- | --------------------------------------------------------------------------------------- |
214
+ | `init` | `() => Promise<void>` | — | Called once per cold start; memoized (call `reset()` to retry) |
215
+ | `request` | `(req) => void` | Buffer-body workaround | Hook called for each request before Express processes it |
216
+ | `response` | `(res) => void` | — | Hook called after Express finishes processing |
217
+ | `serverlessOptions` | `Omit<ServerlessHttp.Options, 'request' \| 'response'>` | — | Additional options forwarded to `serverless-http` (`provider`, `binary`, `basePath`, …) |
218
+ | `maxBodyBytes` | `number` | `1048576` | Skip parsing bodies larger than this in the default `request` hook |
219
+ | `logger` | `Logger` | `console` | Logger used internally |
220
+
221
+ The default `request` hook works around [serverless-http issue #305](https://github.com/dougmoscrop/serverless-http/issues/305)
222
+ by parsing `Buffer` bodies into JSON (when `content-type` starts with
223
+ `application/json`, including charset variations) or UTF-8 strings.
224
+
225
+ #### Netlify example
226
+
227
+ ```ts
228
+ import { createExpressApp, createServerlessHandler } from '@web-ts-toolkit/express-runtime';
229
+ import { Handler } from '@netlify/functions';
230
+
231
+ const app = createExpressApp({
232
+ routers: [{ path: () => '/.netlify/functions/main', handler: myRouter }],
233
+ });
234
+
235
+ export const handler: Handler = createServerlessHandler(app, { init: startDB });
236
+ ```
237
+
238
+ ### `startLocalServer(app, options?): LocalServer`
239
+
240
+ Binds an Express app to a TCP port (or named pipe) via `http.createServer`,
241
+ with friendly error handling and graceful shutdown. Returns `{ server, shutdown }`.
242
+
243
+ | Option | Type | Default | Description |
244
+ | ------------------- | ----------------------------- | ----------------------------- | ----------------------------------------------------------- |
245
+ | `port` | `number \| string` | `process.env.PORT ?? 8080` | Port number or named-pipe path |
246
+ | `host` | `string` | `process.env.HOST ?? 0.0.0.0` | Hostname (ignored for named pipes) |
247
+ | `init` | `() => Promise<void>` | — | Called once before listening |
248
+ | `onShutdown` | `() => Promise<void> \| void` | — | Called on graceful shutdown |
249
+ | `onListening` | `() => void` | — | Called when listening |
250
+ | `onError` | `(error) => void` | logs + exits | Called on server errors |
251
+ | `signals` | `boolean \| NodeJS.Signals[]` | `true` (`SIGINT`, `SIGTERM`) | Signal handlers to register |
252
+ | `shutdownTimeout` | `number` | `5000` | Max ms to wait for in-flight requests before force-closing |
253
+ | `exitAfterShutdown` | `boolean` | `false` | Call `process.exit(0)` after shutdown (the CLI sets `true`) |
254
+ | `logger` | `Logger` | `console` | Logger used internally |
255
+
256
+ #### `LocalServer`
257
+
258
+ | Field | Type | Description |
259
+ | ---------- | --------------------- | ----------------------------------------------------- |
260
+ | `server` | `http.Server` | Underlying HTTP server |
261
+ | `shutdown` | `() => Promise<void>` | Trigger graceful shutdown (drains in-flight requests) |
262
+
263
+ ### `Logger`
264
+
265
+ ```ts
266
+ interface Logger {
267
+ log: (...args: unknown[]) => void;
268
+ error: (...args: unknown[]) => void;
269
+ debug?: (...args: unknown[]) => void;
270
+ }
271
+ ```
272
+
273
+ ## CLI
274
+
275
+ ### `web-ts-toolkit-express-runtime <command> <app-module> [options]`
276
+
277
+ Omitting `<command>` defaults to `dev` for backward compatibility.
278
+
279
+ | Command | Description |
280
+ | ------- | ----------------------------------------------------------------------------------- |
281
+ | `dev` | Run the Express app as a local dev server (`http.createServer` + graceful shutdown) |
282
+ | `build` | Bundle the Express app as a serverless handler using `tsup` |
283
+ | `start` | Run a bundled serverless handler locally (HTTP ↔ serverless event adapter) |
284
+
285
+ #### dev options
286
+
287
+ | Option | Description |
288
+ | ------------------------- | ----------------------------------------------------------------------------------------- |
289
+ | `<app-module>` | Module path whose **default export** is an Express app or an async function returning one |
290
+ | `--port <number>` | Port or named pipe (default: `process.env.PORT` or `8080`) |
291
+ | `--host <hostname>` | Hostname to bind (default: `process.env.HOST` or `0.0.0.0`) |
292
+ | `--no-signals` | Disable `SIGINT` / `SIGTERM` handler registration |
293
+ | `--shutdown-timeout <ms>` | Max ms to wait for in-flight requests (default: `5000`) |
294
+
295
+ #### build options
296
+
297
+ | Option | Description |
298
+ | --------------------- | -------------------------------------------------------------------------------- |
299
+ | `<app-module>` | Module path whose **default export** is an Express app (sync, not async factory) |
300
+ | `--init <path>` | Init hook module (default export, async function) called once per cold start |
301
+ | `--out-dir <path>` | Output directory (default: `dist`) |
302
+ | `--out-name <name>` | Output filename without extension (default: `handler`) |
303
+ | `--format <cjs\|esm>` | Output format (default: `cjs`) |
304
+ | `--target <target>` | Compilation target (default: `node20`) |
305
+ | `--external <pkg>` | Mark package as external (repeatable; `express` is always external) |
306
+ | `--no-clean` | Don't clean the output directory before building |
307
+
308
+ #### start options
309
+
310
+ | Option | Description |
311
+ | ------------------------- | --------------------------------------------------------------------------------- |
312
+ | `<handler-module>` | JS/CJS module path exporting `handler` (named or default) — the output of `build` |
313
+ | `--port <number>` | Port or named pipe (default: `process.env.PORT` or `8080`) |
314
+ | `--host <hostname>` | Hostname to bind (default: `process.env.HOST` or `0.0.0.0`) |
315
+ | `--no-signals` | Disable `SIGINT` / `SIGTERM` handler registration |
316
+ | `--shutdown-timeout <ms>` | Max ms to wait for in-flight requests (default: `5000`) |
317
+
318
+ #### global options
319
+
320
+ | Option | Description |
321
+ | --------------- | --------------------- |
322
+ | `-V, --version` | Print the CLI version |
323
+ | `-h, --help` | Show help |
324
+
325
+ The `dev` command sets `exitAfterShutdown: true` so `SIGINT` / `SIGTERM` cleanly
326
+ exit the process after the server drains. TypeScript app modules require a TS
327
+ loader (see the Quick Start CLI section for a `tsx` invocation).
328
+
329
+ The `build` command generates a temporary entry file that imports the app
330
+ module and wraps it with `createServerlessHandler`, then invokes `tsup` to
331
+ produce a self-contained bundle. `express` is always external; all other
332
+ dependencies (including `@web-ts-toolkit/express-runtime` and `serverless-http`)
333
+ are bundled into the output unless marked external via `--external`.
334
+
335
+ ## License
336
+
337
+ Apache-2.0