BUG: $ref relative paths are relative to CWD, should be relative to current document

[BryanCrotazGivEnergy]

.
|- tools
|    |- bundler.js // contains use of oasNormalize
|- api
     |- my-api.yaml
     |- paths
          |- path.yaml

If my-api.yaml contains a $ref: "./paths/path.yaml" it will fail with

node ./tools/bundler.js ./api/my-api.yaml

But will succeed with

cd ./api
node ../tools/bundler.js ./my-api.yaml

A $ref should be evaluated relative to the currently open file.

My bundler.js code:

import OASNormalize from "oas-normalize";

// if I make next line load ./api/my-openapi.yaml then it will fail to load references
const oas = new OASNormalize("./my-openapi.yaml", {
  enablePaths: true,
});

oas
  .validate()
  .then(() => oas.convert())
  .then((definition) => {
    console.log(definition);
  })
  .catch((err) => {
    console.error(err);
  });

[mscheerschmidt-mhp]

I notice the same behaviour using the verison "oas-normalize": "^14.1.0"

[brain-marchine]

Hi! I ran into the same CWD vs spec-directory $ref resolution issue.

This PR passes the filesystem path through to @readme/openapi-parser for bundle(), dereference(), and validate() when enablePaths is enabled, plus a regression test that bundles external refs without chdir().

Happy to adjust if you'd prefer the fix live in the parser layer instead.

[brain-marchine]

Hi maintainers — CI shows action required for this fork PR (workflows need approval before they can run).
Local verification: npm run check passes (53 tests + build without TS5101).
Could you please approve the workflow run when you have a moment? Thanks!