feat(fromOpenApi): add browser support

[tjosepo]

Closes #49

Changes

• Replaces import { STATUS_CODES } from 'node:http' with import { STATUS_CODES } from './status-codes.js', this way, we don't depend on Node internals.
• Replaces @apidevtools/swagger-parser with a custom JSON Schema dereferencing function that works on the browser
• Adds @stoplight/json to the project, to help with dereferencing JSON schemas.
  • I tried using @stoplight/http-spec as was suggested by @weyert, but it had issues with nested references, required a lot more code change, and was generally lacking in documentation. Using @stoplight/json directly was simpler. With a bit of recursion, the dereferencing algorithm really wasn't that bad.
• All tests are green ✅

Caution

The custom dereferencing function doesn't support remote references.

Only local references are currently supported. I think it's best this way, since figuring out how to support remote references in a way that works on both Node.js and the browser will require more time. Restricting the input while we figure it out seems best.

[weyert]

I think it's a great start to get it working in the browser. Only it doesn't appear to work when using @vitest/browser for me but appears to be related to mswjs itself. Need to play around a bit with that.

[weyert]

I think this is fine for a first iteration. Remote reference can also easily open a can of worms, e.g. from which relative path would it load the remote files etc?

[tjosepo]

I think it's a great start to get it working in the browser. Only it doesn't appear to work when using @vitest/browser for me but appears to be related to mswjs itself. Need to play around a bit with that.

I tested my changes on Chrome using a small OpenAPI spec. It worked. Didn't try it with @vitest/browser.

[weyert]

I think it's a great start to get it working in the browser. Only it doesn't appear to work when using @vitest/browser for me but appears to be related to mswjs itself. Need to play around a bit with that.

I tested my changes on Chrome using a small OpenAPI spec. It worked. Didn't try it with @vitest/browser.

I think this because in Vitest you typically try to use the Node version instead of the browser version needed for @vitest/browser. At least for me it's try to look for mswjs/node

[kettanaito]

I've added a simple browser test using @vitest/browser. It passes locally 🎉

[kettanaito]

This is absolutely incredible! Thank you for your work on this, @tjosepo 👏

[weyert]

Awesome great work! 🚀

[kettanaito]

Released: v0.3.0 🎉

This has been released in v0.3.0!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i @mswjs/source@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.