Closed blikblum closed 2 years ago
This would mean each release even minor ones would be breaking change
Could this be used to get a proper, ES6 (e.g. not needed to Babel-ify) version of Fontkit to be used in modern browders? How do I got about testing this?
While this PR is not merged and released, you can try: https://www.npmjs.com/package/fontkit-next
@blikblum Thanks, using Fontkit-new for the time being. Works nicely.
I agree about deprioritising IE11 in favor of modern browsers!
Anything in particular keeping this from moving forward?
Should be handled as of https://github.com/foliojs/fontkit/pull/276.
Add a browser build that inlines file system data (using brfs) so browser projects using it does not need to use brfs themselves
Created PR on top of #196