next-openapi-gen 1.0.2 → 1.0.4

package/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mariusz Winnik
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -17,6 +17,7 @@ Generate OpenAPI `3.0`, `3.1`, and `3.2` from the routes and schemas you already
 - Target `3.0`, `3.1`, or `3.2` from the same route metadata with version-aware finalization.
 - Ship interactive docs quickly with built-in UI scaffolding for Scalar, Swagger, Redoc, Stoplight Elements, or RapiDoc.
 - Fall back on checker-assisted App Router response inference when explicit `@response` tags are missing.
+- Keep richer Zod 4 and TypeScript output in modern targets with selective runtime-assisted Zod export and checker fallback for advanced type constructs.
 
 ## Quick start
 
@@ -159,6 +160,8 @@ See [apps/next-app-mixed-schemas](./apps/next-app-mixed-schemas) for a full work
 For more adoption patterns, see
 [docs/workflows-and-integrations.md](./docs/workflows-and-integrations.md).
 
+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.
+
 ### Generate docs from Drizzle schemas
 
 `next-openapi-gen` works well with `drizzle-zod`, so your database schema, validation, and API docs can share the same source of truth.

package/bin/cli.mjs

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+
+import fs from "node:fs";
+
+const cliModuleUrl = new URL("../dist/cli.js", import.meta.url);
+
+if (!fs.existsSync(cliModuleUrl)) {
+  process.stderr.write(
+    "The next-openapi-gen CLI has not been built yet. Run `pnpm exec turbo run build --filter=next-openapi-gen...` first.\n",
+  );
+  process.exit(1);
+}
+
+await import(cliModuleUrl.href);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-openapi-gen",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Automatically generate OpenAPI 3.0, 3.1, and 3.2 documentation from Next.js projects, with support for Zod schemas, TypeScript types, and reusable OpenAPI fragments.",
   "keywords": [
     "api",
@@ -23,10 +23,11 @@
     "url": "git+ssh://git@github.com/tazo90/next-openapi-gen.git"
   },
   "bin": {
-    "next-openapi-gen": "./dist/cli.js",
-    "openapi-gen": "./dist/cli.js"
+    "next-openapi-gen": "./bin/cli.mjs",
+    "openapi-gen": "./bin/cli.mjs"
   },
   "files": [
+    "bin",
     "dist",
     "templates",
     "README.md"
@@ -71,8 +72,8 @@
     "@types/node": "^25.5.0",
     "conventional-changelog-cli": "^5.0.0",
     "np": "^11.0.2",
-    "oxfmt": "^0.42.0",
-    "oxlint": "^1.57.0",
+    "oxfmt": "^0.43.0",
+    "oxlint": "^1.58.0",
     "tsup": "^8.5.1"
   },
   "engines": {