next-openapi-gen 1.0.3 → 1.0.5
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 +3 -0
- package/dist/cli.js +8579 -646
- package/dist/index.js +8587 -653
- package/dist/next/index.js +8577 -625
- package/dist/react-router/index.js +8356 -462
- package/dist/vite/index.js +8356 -462
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -17,6 +17,7 @@ Generate OpenAPI `3.0`, `3.1`, and `3.2` from the routes and schemas you already
|
|
|
17
17
|
- Target `3.0`, `3.1`, or `3.2` from the same route metadata with version-aware finalization.
|
|
18
18
|
- Ship interactive docs quickly with built-in UI scaffolding for Scalar, Swagger, Redoc, Stoplight Elements, or RapiDoc.
|
|
19
19
|
- Fall back on checker-assisted App Router response inference when explicit `@response` tags are missing.
|
|
20
|
+
- Keep richer Zod 4 and TypeScript output in modern targets with selective runtime-assisted Zod export and checker fallback for advanced type constructs.
|
|
20
21
|
|
|
21
22
|
## Quick start
|
|
22
23
|
|
|
@@ -159,6 +160,8 @@ See [apps/next-app-mixed-schemas](./apps/next-app-mixed-schemas) for a full work
|
|
|
159
160
|
For more adoption patterns, see
|
|
160
161
|
[docs/workflows-and-integrations.md](./docs/workflows-and-integrations.md).
|
|
161
162
|
|
|
163
|
+
When you target modern OpenAPI output, the Zod path can also split request and response component refs when a supported Zod 4 schema emits different input and output JSON Schema shapes, while the TypeScript path can use selective checker fallback for mapped, conditional, template-literal, and import-based named types.
|
|
164
|
+
|
|
162
165
|
### Generate docs from Drizzle schemas
|
|
163
166
|
|
|
164
167
|
`next-openapi-gen` works well with `drizzle-zod`, so your database schema, validation, and API docs can share the same source of truth.
|