moo
moo copied to clipboard
Provide ESM bundle
Most popular packages have moved on to ESM-only or dual export packages. Moo is still using the old-fashioned UMD format, being not-really-compatible with modern tooling.
Hi, can you give an example of tooling that is not compatible with Moo today?
I imagine "not-really-compatible" here means "it works completely fine and my packaging script can't exclude compileStates" or "it works completely fine and my editor can't autocomplete the entry point names"
Yeah, without ESM bundle it cannot be tree-shaken... but looking at the source, I'm not sure how much there could be shaken away anyway..?
ESM would allow this, which is a style I use all the time:
import {compile} from 'moo';