@rexeus/typeweaver-server 0.5.1

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/README.md ADDED
@@ -0,0 +1,393 @@
1
+ # ๐Ÿงตโœจ @rexeus/typeweaver-server
2
+
3
+ [![npm version](https://img.shields.io/npm/v/@rexeus/typeweaver-server.svg)](https://www.npmjs.com/package/@rexeus/typeweaver-server)
4
+ [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
5
+ [![TypeScript](https://img.shields.io/badge/TypeScript-Ready-blue.svg)](https://www.typescriptlang.org/)
6
+
7
+ Typeweaver is a type-safe HTTP API framework built for API-first development with a focus on
8
+ developer experience. Use typeweaver to specify your HTTP APIs in TypeScript and Zod, and generate
9
+ clients, validators, routers, and more โœจ
10
+
11
+ ## ๐Ÿ“ Server Plugin
12
+
13
+ This plugin generates a **lightweight, dependency-free server** with built-in routing and middleware
14
+ from your typeweaver API definitions. No external framework required โ€” everything runs on the
15
+ standard Fetch API (`Request`/`Response`).
16
+
17
+ For each resource, it produces a `<ResourceName>Router` class that registers routes, validates
18
+ requests, and wires your handler methods with full type safety. Mount routers on the provided
19
+ `TypeweaverApp` to get a complete server with middleware support.
20
+
21
+ > Choose this plugin for a zero-dependency, Fetch API-native server. For Hono framework integration,
22
+ > see [@rexeus/typeweaver-hono](../hono/README.md).
23
+
24
+ ### Key Features
25
+
26
+ - **Zero runtime dependencies** โ€” no Hono, Express, or Fastify required
27
+ - **Fetch API compatible** โ€” works with Bun, Deno, Cloudflare Workers, and Node.js (>=18)
28
+ - **High-performance radix tree router** โ€” O(d) lookup where d = number of path segments
29
+ - **Type-safe middleware** โ€” compile-time state guarantees via `defineMiddleware`, `StateMap`, and
30
+ `InferState`
31
+ - **Automatic HEAD handling** โ€” falls back to GET handlers per HTTP spec
32
+ - **405 Method Not Allowed** โ€” with proper `Allow` header
33
+
34
+ ---
35
+
36
+ ## ๐Ÿ“ฅ Installation
37
+
38
+ ```bash
39
+ # Install the CLI and the plugin as a dev dependency
40
+ npm install -D @rexeus/typeweaver @rexeus/typeweaver-server
41
+
42
+ # Install the runtime as a dependency
43
+ npm install @rexeus/typeweaver-core
44
+ ```
45
+
46
+ ## ๐Ÿ’ก How to use
47
+
48
+ ```bash
49
+ npx typeweaver generate --input ./api/definition --output ./api/generated --plugins server
50
+ ```
51
+
52
+ More on the CLI in
53
+ [@rexeus/typeweaver](https://github.com/rexeus/typeweaver/tree/main/packages/cli/README.md#๏ธ-cli).
54
+
55
+ ## ๐Ÿ“‚ Generated Output
56
+
57
+ For a resource `User`, the plugin generates:
58
+
59
+ ```
60
+ generated/
61
+ lib/server/ โ† TypeweaverApp, middleware types, etc.
62
+ user/
63
+ UserRouter.ts โ† Router class + UserApiHandler type
64
+ GetUserRequest.ts โ† Request types (IGetUserRequest)
65
+ GetUserResponse.ts โ† Response types + factory classes
66
+ ...
67
+ ```
68
+
69
+ Import `TypeweaverApp`, routers, and types from `./generated`.
70
+
71
+ ## ๐Ÿš€ Usage
72
+
73
+ ### Implement handlers
74
+
75
+ Each handler receives the typed request and returns a typed response โ€” plain objects with
76
+ `statusCode`, `header`, and `body`. Content-Type is auto-set to `application/json` for object
77
+ bodies.
78
+
79
+ ```ts
80
+ // user-handlers.ts
81
+ import { HttpStatusCode } from "@rexeus/typeweaver-core";
82
+ import type { UserApiHandler } from "./generated";
83
+
84
+ export const userHandlers: UserApiHandler = {
85
+ async handleListUsersRequest() {
86
+ return {
87
+ statusCode: HttpStatusCode.OK,
88
+ body: [{ id: "1", name: "Jane", email: "jane@example.com" }],
89
+ };
90
+ },
91
+
92
+ async handleCreateUserRequest(request) {
93
+ return {
94
+ statusCode: HttpStatusCode.CREATED,
95
+ body: { id: "1", name: request.body.name, email: request.body.email },
96
+ };
97
+ },
98
+
99
+ async handleGetUserRequest(request) {
100
+ return {
101
+ statusCode: HttpStatusCode.OK,
102
+ body: { id: request.param.userId, name: "Jane", email: "jane@example.com" },
103
+ };
104
+ },
105
+
106
+ async handleDeleteUserRequest() {
107
+ return { statusCode: HttpStatusCode.NO_CONTENT };
108
+ },
109
+ };
110
+ ```
111
+
112
+ > Generated response classes (e.g. `GetUserSuccessResponse`) are also available for when you need
113
+ > runtime type checks or `instanceof` discrimination in error handling.
114
+
115
+ ### Create the app
116
+
117
+ ```ts
118
+ // server.ts
119
+ import { TypeweaverApp, UserRouter } from "./generated";
120
+ import { userHandlers } from "./user-handlers";
121
+
122
+ const app = new TypeweaverApp();
123
+ app.route(new UserRouter({ requestHandlers: userHandlers }));
124
+
125
+ export default app;
126
+ ```
127
+
128
+ ### Start the server
129
+
130
+ **Bun**
131
+
132
+ ```ts
133
+ import app from "./server";
134
+
135
+ Bun.serve({ fetch: app.fetch, port: 3000 });
136
+ ```
137
+
138
+ **Deno**
139
+
140
+ ```ts
141
+ import app from "./server.ts";
142
+
143
+ Deno.serve({ port: 3000 }, app.fetch);
144
+ ```
145
+
146
+ **Node.js**
147
+
148
+ ```ts
149
+ import { createServer } from "node:http";
150
+ import { nodeAdapter } from "./generated/lib/server";
151
+ import app from "./server";
152
+
153
+ createServer(nodeAdapter(app)).listen(3000);
154
+ ```
155
+
156
+ ### Multiple routers
157
+
158
+ ```ts
159
+ app.route(new UserRouter({ requestHandlers: userHandlers }));
160
+ app.route("/api/v1", new OrderRouter({ requestHandlers: orderHandlers }));
161
+ ```
162
+
163
+ ### ๐Ÿ”— Middleware
164
+
165
+ Middleware is defined with `defineMiddleware` and follows a return-based onion model. Each
166
+ middleware declares what state it **provides** downstream and what state it **requires** from
167
+ upstream โ€” all checked at compile time.
168
+
169
+ **Providing state** โ€” pass state to `next()`:
170
+
171
+ ```ts
172
+ import { defineMiddleware } from "./generated/lib/server";
173
+
174
+ const auth = defineMiddleware<{ userId: string }>(async (ctx, next) => {
175
+ const token = ctx.request.header?.["authorization"];
176
+ return next({ userId: parseToken(token) });
177
+ });
178
+ ```
179
+
180
+ When `TProvides` has keys, `next()` **requires** the state object as its argument โ€” you can't forget
181
+ to provide it.
182
+
183
+ **Requiring upstream state** โ€” declare dependencies:
184
+
185
+ ```ts
186
+ const permissions = defineMiddleware<{ permissions: string[] }, { userId: string }>(
187
+ async (ctx, next) => {
188
+ const userId = ctx.state.get("userId"); // string โ€” no cast, no undefined
189
+ return next({ permissions: await loadPermissions(userId) });
190
+ }
191
+ );
192
+ ```
193
+
194
+ Registering `permissions` before `auth` produces a **compile-time error** because `userId` is not
195
+ yet available in the accumulated state.
196
+
197
+ **Pass-through middleware** โ€” `next()` takes no arguments:
198
+
199
+ ```ts
200
+ const logger = defineMiddleware(async (ctx, next) => {
201
+ const start = Date.now();
202
+ const response = await next();
203
+ console.log(
204
+ `${ctx.request.method} ${ctx.request.path} -> ${response.statusCode} (${Date.now() - start}ms)`
205
+ );
206
+ return response;
207
+ });
208
+ ```
209
+
210
+ **Short-circuit** โ€” return a response without calling `next()`:
211
+
212
+ ```ts
213
+ const guard = defineMiddleware(async (ctx, next) => {
214
+ if (!ctx.request.header?.["authorization"]) {
215
+ return { statusCode: 401, body: { message: "Unauthorized" } };
216
+ }
217
+ return next();
218
+ });
219
+ ```
220
+
221
+ **Path-scoped guard** โ€” use `pathMatcher` to limit middleware to specific routes:
222
+
223
+ ```ts
224
+ import { defineMiddleware, pathMatcher } from "./generated/lib/server";
225
+
226
+ const isUsersPath = pathMatcher("/users/*");
227
+
228
+ const usersGuard = defineMiddleware(async (ctx, next) => {
229
+ if (!isUsersPath(ctx.request.path)) return next();
230
+ if (!ctx.request.header?.["authorization"]) {
231
+ return { statusCode: 401, body: { message: "Unauthorized" } };
232
+ }
233
+ return next();
234
+ });
235
+ ```
236
+
237
+ `pathMatcher` supports exact matches (`"/health"`) and prefix matches (`"/users/*"`).
238
+
239
+ **Chaining** โ€” state accumulates through `.use()`:
240
+
241
+ ```ts
242
+ const app = new TypeweaverApp()
243
+ .use(auth) // provides { userId: string }
244
+ .use(permissions) // requires { userId }, provides { permissions: string[] }
245
+ .route(new TodoRouter({ requestHandlers: todoHandlers }));
246
+ ```
247
+
248
+ **`InferState`** โ€” extract the accumulated state type for handlers:
249
+
250
+ ```ts
251
+ import type { InferState } from "./generated/lib/server";
252
+
253
+ type AppState = InferState<typeof app>;
254
+ // { userId: string } & { permissions: string[] }
255
+ ```
256
+
257
+ Middleware runs for **all** requests, including 404s and 405s, so global concerns like logging and
258
+ CORS always execute.
259
+
260
+ ### ๐Ÿ› ๏ธ App Options
261
+
262
+ `TypeweaverApp` accepts an optional options object:
263
+
264
+ | Option | Type | Default | Description |
265
+ | ------------- | -------------------------- | ------------------ | ----------------------------------------------------------- |
266
+ | `maxBodySize` | `number` | `1_048_576` (1 MB) | Max request body size in bytes. Exceeding returns `413`. |
267
+ | `onError` | `(error: unknown) => void` | `console.error` | Error callback. Falls back to `console.error` if it throws. |
268
+
269
+ ```ts
270
+ const app = new TypeweaverApp({
271
+ maxBodySize: 5 * 1024 * 1024, // 5 MB
272
+ onError: error => logger.error("Unhandled error", error),
273
+ });
274
+ ```
275
+
276
+ ### โš™๏ธ Router Configuration
277
+
278
+ Each router accepts `TypeweaverRouterOptions`:
279
+
280
+ | Option | Type | Default | Description |
281
+ | -------------------------- | ---------------------- | ---------- | ---------------------------------- |
282
+ | `requestHandlers` | `<Resource>ApiHandler` | _required_ | Handler methods for each operation |
283
+ | `validateRequests` | `boolean` | `true` | Enable/disable request validation |
284
+ | `handleValidationErrors` | `boolean \| function` | `true` | Handle validation errors |
285
+ | `handleHttpResponseErrors` | `boolean \| function` | `true` | Handle thrown `HttpResponse` |
286
+ | `handleUnknownErrors` | `boolean \| function` | `true` | Handle unexpected errors |
287
+
288
+ When set to `true`, error handlers use sensible defaults (400/500 responses). When set to `false`,
289
+ errors fall through to the next handler in the chain. When set to a function, it receives the error
290
+ and `ServerContext` and must return an `IHttpResponse`.
291
+
292
+ ### ๐Ÿšจ Error Handling
293
+
294
+ #### Throwing errors in handlers
295
+
296
+ All generated error response classes (e.g. `NotFoundErrorResponse`, `ValidationErrorResponse`)
297
+ extend `HttpResponse`. Throw them in your handlers โ€” the framework catches them automatically:
298
+
299
+ ```ts
300
+ import { HttpStatusCode } from "@rexeus/typeweaver-core";
301
+ import { GetUserSuccessResponse, NotFoundErrorResponse } from "./generated";
302
+
303
+ async handleGetUserRequest(request) {
304
+ const user = await db.findUser(request.param.userId);
305
+ if (!user) {
306
+ throw new NotFoundErrorResponse({
307
+ statusCode: HttpStatusCode.NOT_FOUND,
308
+ header: { "Content-Type": "application/json" },
309
+ body: { message: "Resource not found", code: "NOT_FOUND_ERROR" },
310
+ });
311
+ }
312
+ return new GetUserSuccessResponse({
313
+ statusCode: HttpStatusCode.OK,
314
+ header: { "Content-Type": "application/json" },
315
+ body: user,
316
+ });
317
+ }
318
+ ```
319
+
320
+ When `handleHttpResponseErrors` is `true` (the default), thrown `HttpResponse` instances are
321
+ returned as-is. No extra configuration needed.
322
+
323
+ #### Custom error mapping
324
+
325
+ Use custom handler functions to transform errors into your own response shape.
326
+
327
+ **Validation errors** โ€” map framework validation errors to your spec-defined format:
328
+
329
+ ```ts
330
+ new UserRouter({
331
+ requestHandlers: userHandlers,
332
+ handleValidationErrors: (error, ctx) =>
333
+ new ValidationErrorResponse({
334
+ statusCode: HttpStatusCode.BAD_REQUEST,
335
+ header: { "Content-Type": "application/json" },
336
+ body: {
337
+ code: "VALIDATION_ERROR",
338
+ message: "Request is invalid",
339
+ issues: {
340
+ body: error.bodyIssues,
341
+ query: error.queryIssues,
342
+ param: error.pathParamIssues,
343
+ header: error.headerIssues,
344
+ },
345
+ },
346
+ }),
347
+ });
348
+ ```
349
+
350
+ **HTTP response errors** โ€” log thrown errors and pass them through:
351
+
352
+ ```ts
353
+ new UserRouter({
354
+ requestHandlers: userHandlers,
355
+ handleHttpResponseErrors: (error, ctx) => {
356
+ logger.warn("HTTP error", { status: error.statusCode, path: ctx.request.path });
357
+ return error;
358
+ },
359
+ });
360
+ ```
361
+
362
+ **Unknown errors** โ€” catch unexpected failures and return a safe response:
363
+
364
+ ```ts
365
+ new UserRouter({
366
+ requestHandlers: userHandlers,
367
+ handleUnknownErrors: (error, ctx) => {
368
+ logger.error("Unhandled error", { error, path: ctx.request.path });
369
+ return new InternalServerErrorResponse({
370
+ statusCode: HttpStatusCode.INTERNAL_SERVER_ERROR,
371
+ header: { "Content-Type": "application/json" },
372
+ body: { code: "INTERNAL_SERVER_ERROR", message: "Something went wrong" },
373
+ });
374
+ },
375
+ });
376
+ ```
377
+
378
+ ### ๐Ÿ“‹ Error Responses
379
+
380
+ | Status | Code | When |
381
+ | ------ | ----------------------- | ------------------------------------------------------------- |
382
+ | `400` | `BAD_REQUEST` | Malformed request body |
383
+ | `400` | Validation issues | `handleValidationErrors: true` and request fails validation |
384
+ | `404` | `NOT_FOUND` | No matching route |
385
+ | `405` | `METHOD_NOT_ALLOWED` | Route exists but method not allowed (includes `Allow` header) |
386
+ | `413` | `PAYLOAD_TOO_LARGE` | Request body exceeds `maxBodySize` |
387
+ | `500` | `INTERNAL_SERVER_ERROR` | Unhandled error in handler |
388
+
389
+ All error responses follow the shape: `{ code: string, message: string }`.
390
+
391
+ ## ๐Ÿ“„ License
392
+
393
+ Apache 2.0 ยฉ Dennis Wentzien 2026
package/dist/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 Dennis Wentzien
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/dist/NOTICE ADDED
@@ -0,0 +1,4 @@
1
+ Copyright 2026 Dennis Wentzien
2
+
3
+ This project is licensed under the Apache License, Version 2.0
4
+ See LICENSE file for details.