JonLuca De Caro

If you could provide the schemas that cause the issue we could debug it and add a test case

This looks like a bug with https://www.jsonschemavalidator.net/ - what part of the json schema is invalid? It's a $ref that points to another $ref, with a few layers of indirection,...

 Yes, the issue occurs there as well. The proposed workaround works though, for what its worth.

 Same issue

 New error this time haha

 Same issue A way to debug might be to use bun - ```js import { parseBlob } from "music-metadata"; import { promises as fs } from "fs"; const data...

I dont believe the site has an updated build - it's the same error as earlier. However testing with main with bun seems to be working? I've created a PR...

Were you able to figure this out @JacobJaffe?

Thanks for the PR! Merged in

I added a named export - could try ```import { convert } from '@openapi-contrib/json-schema-to-openapi-schema'``` in v4.0.0?