Consider making it compatible with browsers

[fmvilas]

Hi, I like this package a lot but I've seen there are many dependencies that while they may be compatible with a browser through Browserify or similar, it makes the package unnecessarily big for such environment.

Have you considered making a lightweight browser-compatible version?

[torifat]

We didn't think about it since we mostly built it to use it in backend. But most of bloats are coming from dependencies we use to make things look nicer in cli. So, it's possible to split things in smaller packages so that people can use only the parsing logic in browser. Thanks for raising it. I will give it shot.

[fmvilas]

This would be amazing. I would like to help with this but I'd lie if I tell you I'll have time 😄. In case it helps, we'd like to use it as part of our AsyncAPI Javascript parser which must be browser-compatible for apps like playground.asyncapi.io.

[buremba]

Are there any plans for this feature request?

[jrebmann]

This function would be very nice.
I want to use the ajv-json validation in my browser application, and better-ajv-errors is a very nice way to embellish the error messages for my end users.

Also, I don't see any reason why the framework shouldn't be usable in the browser as well, since no system resources need to be accessed. Furthermore ajv is browser compatible, so better-ajv-errors would cover a much wider range of applications.