Behavior change for relative input path in 0.26.0

[bdbvb]

After updating from 0.25.0 to 0.26.0, a relative path passed to the input parameter is resolved from the "node_modules@apidevtools\json-schema-ref-parser" folder instead of from the project folder where the command is being run.

Example command:

openapi --input ./openapi/swagger-design.json --output ./openapi-gen --name FooBar

It tries to read from

node_modules\@apidevtools\json-schema-ref-parse\openapi\swagger-design.json

and gives an error that it cannot find that file (because the file is actually under my project folder).

{
  stack: 'JSONParserError: Error opening file "C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json" \n' +
    "ENOENT: no such file or directory, open 'C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json'\n" +
    '    at Object.read (C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\lib\\resolvers\\file.js:59:19)',
  code: 'ERESOLVER',
  name: 'ResolverError',
  message: 'Error opening file "C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json" \n' +
    "ENOENT: no such file or directory, open 'C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json'",
  source: 'C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json',
  path: null,
  toJSON: [Function: toJSON],
  ioErrorCode: 'ENOENT',
  footprint: 'null+C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json+ERESOLVER+Error opening file "C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json" \n' +
    "ENOENT: no such file or directory, open 'C:\\Projects\\Foo\\MyProjectFolder\\node_modules\\@apidevtools\\json-schema-ref-parser\\dist\\openapi\\swagger-design.json'",
  toString: [Function: toString]
}

[Spajker7]

I am also experiencing this issue

[Delevin888]

same issue.

[sander-b-postnl]

apidevtools/json-schema-ref-parse#311 the issue seems to be related to this one.

[ferdikoomen]

Seems indeed a json-schema-ref-parse issue, checking now

[ferdikoomen]

Easy solution for now, would be to revert json-schema-ref-parse to 10.1.0 until they fix the issue. I will do that and publish a new release.

[ferdikoomen]

Created a new release (0.27.0) https://github.com/ferdikoomen/openapi-typescript-codegen/releases/tag/v.027.0 please check if that resolves the issue

[derBinder]

It doesn't fix the issue.

[kumv-net]

Created a new release (0.27.0) https://github.com/ferdikoomen/openapi-typescript-codegen/releases/tag/v.027.0 please check if that resolves the issue

hey，It doesn't fix the issue. try revert json-schema-ref-parse to 11.0.0

https://github.com/APIDevTools/json-schema-ref-parser/releases/tag/v11.0.0

Fix windows paths and external refs (APIDevTools/json-schema-ref-parser#321) (b9f91b2), closes APIDevTools/json-schema-ref-parser#321
BREAKING CHANGES
Change the file path parsing logic (to be safe)

[kumv-net]

json-schema-ref-parser
i use openapi-typescript-codegen@0.25.0 json-schema-ref-parser@9.0.9

[nruffing]

Looking at the RefParser.parse implementation it looks getOpenApiSpec needs to be passing in a base path for relative paths to be resolved against and the recommended use case is to pass in a full file url.

openapi-typescript-codegen/src/utils/getOpenApiSpec.ts

Line 3 in 31632d4

/**

https://github.com/APIDevTools/json-schema-ref-parser/blob/main/lib/index.ts#L58

[bdbvb]

I should also note that, even if I pass an absolute path to --input, it still tries to append that to node_modules\@apidevtools\json-schema-ref-parser\dist.

The only workaround I can come up with is to use ../../../.. instead of . in front of my relative input path.

Curious how other people are getting this to work without the above hack, as otherwise the library appears to be unusable when using an input file. (Of course, downgrading is also an option, but not a nice one.)

[WillGarman]

I was on 0.27.0 when I was getting this error. Downgraded to 0.25.0, worked perfect

[mahdibx]

We had to downgrade too, tried the absolute path and overriding to the latest version of json-schema-ref-parser (11.1.0), still it just appends the absolute path to the package folder, really odd way of handling paths, wondering how this works for anyone.

[LEI]

This problem occured on Windows but not macOS, downgrading the package to 0.25 fixed it.