NPM errors installing @nahkies/openapi-code-generator

[gunzip]

Hi! I've tried following the quickstart but I get this when installing the package:

vscode ➜ /tmp/test $ npm i --save-dev @nahkies/openapi-code-generator
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: @typespec/sse@0.77.0
npm error node_modules/@typespec/sse
npm error   peerOptional @typespec/sse@"^0.77.0" from @typespec/openapi3@1.7.0
npm error   node_modules/@typespec/openapi3
npm error     peerOptional @typespec/openapi3@"^1.1.0" from @nahkies/openapi-code-generator@0.22.0
npm error     node_modules/@nahkies/openapi-code-generator
npm error       dev @nahkies/openapi-code-generator@"*" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @typespec/sse@"^0.72.1" from @nahkies/openapi-code-generator@0.22.0
npm error node_modules/@nahkies/openapi-code-generator
npm error   dev @nahkies/openapi-code-generator@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/vscode/.npm/_logs/2025-12-30T16_41_56_489Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/vscode/.npm/_logs/2025-12-30T16_41_56_489Z-debug-0.log

1 info using npm@10.9.4
2 info using node@v22.21.1

[mnahkies]

Ah yikes, sorry I thought I'd squashed those peerDependency mismatch issues. Might need to devise some CI steps that use all the popular package managers to properly prevent them creeping back in.

I'd suggest trying the --force / --legacy-peer-deps options suggested in the error output for now, if you're not using a typespec input those peer dependencies are optional anyway, and even if you are using typespec it will likely still work I think.

I've got a reasonably big release in the works for hopefully this week or next, so will add this to the list of things to check prior to that.

[gunzip]

Thank you, great work! I’m working on a project very similar to yours. If your project had been further along back in August, I probably wouldn’t have even started mine, as many of our design choices and technical challenges seem to align.

Unrelated: one thing I had to reconsider recently is that OpenAPI status codes aren't always numeric; they can be strings (like 'default' or wildcards like '5XX'). This forced me to refactor them from integers to strings. I wanted to see how openapi-code-generator handles this case, so I’m going to try installing it following your instructions :-)

[mnahkies]

At the moment it'll basically prefer an exact match for the status code (if a response with that specific code is defined in the spec), otherwise use the Nxx response, before finally matching against the default response if one is specified.

References:
https://github.com/mnahkies/openapi-code-generator/blob/main/integration-tests%2Ftypescript-koa%2Fsrc%2Fgenerated%2Ftodo-lists.yaml%2Fgenerated.ts#L326-L332

https://github.com/mnahkies/openapi-code-generator/blob/main/packages%2Ftypescript-koa-runtime%2Fsrc%2Fzod-v4.ts#L29-L54

There's a lot to implement - it'll probably be forever a work in progress 😂