Blake Embrey

Although this would be the preferred fix overall (especially for non-JS users), I'd like to ensure we don't break the JavaScript functionality.

RAML 1.0 is not supported yet, we're working on building a RAML 1.0 parser in Java right now.

> can you have a look? Seems correct to me, it's likely I wrote this out of order and didn't know that limitation - is it as easy as switching...

This library converts a string to a string, I'd just use this directly instead: https://github.com/borderless/base64. It converts between `ArrayBuffer` directly so no need to encode/decode, which should eliminate this bug...

@Inrmanish This has nothing to do with same origin policy, it’s running in node.js.

Thanks for the PR @MaoShizhong, I'm going to land this now as it looks useful for a 1.0 release. I am going to make the error message formats consistent though,...

Adding code is definitely useful but it can be added later as a backward compatible change, so I'm going to wait until we align on whether we want that for...

You're welcome to open a PR for this. I'm not familiar with those languages to know what the "small words" list should be, but I believe everything else already works.

@hxtruong6 that is unrelated to the original report so I’ll be hiding the comment. Try searching closed issues instead, it’s because your typescript configuration is incorrect for ESM support.

I think I closed a past issue on the complexity on typing these, but I think it could be good to have available. I would accept a PR if anyone...