Hi there!
I'm using this package on the front-end, and want to optimize my bundles sizes. In order to do so, I would need this package to be exported as an ES module that can be tree-shaken for unused stuff.
I can do a PR to build this package as both CJS and ESM, and configure proper exports. Most things should be backwards-compatible, with the exception of the Grammar exports where each grammar would be exported separately. This would allow unused grammars to be removed. Typescript support would be keept, of course.
What do you think about this?
Hi there!
I'm using this package on the front-end, and want to optimize my bundles sizes. In order to do so, I would need this package to be exported as an ES module that can be tree-shaken for unused stuff.
I can do a PR to build this package as both CJS and ESM, and configure proper exports. Most things should be backwards-compatible, with the exception of the
Grammarexports where each grammar would be exported separately. This would allow unused grammars to be removed. Typescript support would be keept, of course.What do you think about this?