value?.ref?.split is not a function when using the validate command

[antoinebidault]

Hi,
Since updating the CLI to v10, my OpenAPI specs fail to validate from this URL:
🔗 https://api.dastra.eu/api/v1/dastra.json

This worked fine in v9.0.5, and manually uploading the specs to the dashboard still works.

Steps to Reproduce
Installation method: npm i rdme -g
Specs validation : rdme openapi validate https://api.dastra.eu/api/v1/dastra.json
Screenshot of the issue:

It seems to be related to the ref parser lib

Environment
Node version : 22.11.0
Npm version : 10.9.0

[m1k3lm]

Hi,

We're encountering the same error with our schemas. What's particularly strange is that the issue appears inconsistently—some machines experience it while others do not, despite using the same Node, npm, and rdme versions. We were able to reproduce the same behavior with both your OpenAPI file and ours.

To further investigate, we tested using the official Docker images, and the validation error persists across versions:

• With the latest rdme:

  docker run --rm node:22 sh -c "npx rdme openapi:validate https://api.dastra.eu/api/v1/dastra.json"

• Even with rdme 9.0.5:

  docker run --rm node:22 sh -c "npx rdme@9.0.5 openapi:validate https://api.dastra.eu/api/v1/dastra.json"

• Testing with an updated npm version:

  docker run --rm node:22 sh -c "npm install -g npm@11.1.0 && npx rdme@9.0.5 openapi:validate https://api.dastra.eu/api/v1/dastra.json"

• And with the latest npm:

  docker run --rm node sh -c "npm install -g npm@11.1.0 && npx rdme openapi:validate https://api.dastra.eu/api/v1/dastra.json"

Additionally, we noticed this deprecation warning, which might be related:

npm WARN deprecated @readme/json-schema-ref-parser@1.2.1: This package is no longer maintained. Please use @apidevtools/json-schema-ref-parser instead.

For reference, here's one of our openapi.json.

Let us know if you find any further insights!

[m1k3lm]

It seems that this will be fixed in the 10.2 version.

docker run --rm node sh -c "npx rdme@10.2.0-next.5 openapi:validate https://api.dastra.eu/api/v1/dastra.json" 

returns

• Validating the API definition located at https://api.dastra.eu/api/v1/dastra.json...
  https://api.dastra.eu/api/v1/dastra.json is a valid OpenAPI API definition!

[kanadgupta]

Hi folks! We've been overhauling our OpenAPI / JSON schema parsing and the changes landed in #1189. It looks like @m1k3lm confirmed that the issue is fixed in rdme@10.2.0-next.5 (npm release, GitHub release). Please upgrade to this version in the meantime. A release on the latest channel with this fix should be available soon.

I'll close this out now but please reach out if you see any other issues. Thanks!