Error generating API - cannot find file

[snisar]

I and a colleague have both started encountering this error when trying to generate API's.

Error on API generation from http://localhost:5000/swagger/v1/swagger.json: ResolverError: Error downloading http://localhost:5000/swagger/v1/swagger.json
fetch failed

Browsing to the file specified in the error above works fine.

If I change the location to a file in a directory, that also does not work.

config file:
{"input": "c:/temp/swagger.json", "output": "app/api", "ignoreUnusedModels": false }

Output

Error on API generation from c:/temp/swagger.json: ResolverError: Error opening file "F:\AgVentory\ClientApp\node_modules@apidevtools\json-schema-ref-parser\c:\temp\swagger.json"
ENOENT: no such file or directory, open 'F:\AgVentory\ClientApp\node_modules@apidevtools\json-schema-ref-parser\c:\temp\swagger.json'

Not sure what has changed to cause these errors.

[luisfpg]

Which generator version are you using? Em qui., 2 de fev. de 2023 12:27, Saquib Nisar ***@***.***> escreveu:

…

I and a colleague have both started encountering this error when trying to generate API's. Error on API generation from http://localhost:5000/swagger/v1/swagger.json: ResolverError: Error downloading http://localhost:5000/swagger/v1/swagger.json fetch failed Browsing to the file specified in the error above works fine. If I change the location to a file in a directory, that also does not work. config file: "input": "c:/temp/swagger.json", "output": "app/api", "ignoreUnusedModels": false } Output Error on API generation from c:/temp/swagger.json: ResolverError: Error opening file ***@***.*** \json-schema-ref-parser\c:\temp\swagger.json" ENOENT: no such file or directory, open ***@***.*** \json-schema-ref-parser\c:\temp\swagger.json' Not sure what has changed to cause these errors. — Reply to this email directly, view it on GitHub <#261>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJA76LW6ZNK4OIKUZOOBXTWVPG5ZANCNFSM6AAAAAAUPFL2ZU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[snisar]

0.23.0

[luisfpg]

It should be something with the Windows syntax (somehow it is trying c:/temp/swagger.json as a relative path).
I don't use Windows myself, and can't help so much more with this... Sorry.

[unknownbanana]

Same issue here but, using a relative path.
We're on version: 0.53.0, and version: 11.2.0 of @apidevtools/json-schema-ref-parser.
We're using PNPM 9.3.0.

@snisar We're about 2 years along so this may be a futile question, did you end up fixing this, as far as you can remember?

[snisar]

Sorry I think it went away itself and I don't know why 😞

[unknownbanana]

@snisar Ah damn it, thanks for the answer anyway much appreciated!

[unknownbanana]

Just resolved this by overriding the @apidevtools/json-schema-ref-parser to version 11.9.3.
Seems to have been fixed in 11.1.0 however we had previously overridden to 11.2.0 and the issue still occurred there. [ https://github.com/APIDevTools/json-schema-ref-parser/issues/311 ]

@luisfpg Would like to request that the @apidevtools/json-schema-ref-parser dependency gets bumped to either 11.x or 12.x. It contains several CVE fixes (which is why have overridden the version) and ng-openapi-gen is currently 3 major versions behind.