Move the library to ES6 modules.
However, this will result in issues for consumers not capable of using ES6: As far as I can see, we're currently not transpiling our code before pushing it to npm. This means, that consumers requiring the "lib" are only getting ES6 which may result in runtime errors, unless the consumer itself transpiles the code to CJS.
=>
Either transpile this complete application before publishing to npm (a .npmignore has to be implemented, as well as a prepublish command)
OR
Extract the parser from both the projects and create a third one which only publishes the parser to NPM. @jschirrmacher wdyt?
Move the library to ES6 modules. However, this will result in issues for consumers not capable of using ES6: As far as I can see, we're currently not transpiling our code before pushing it to npm. This means, that consumers requiring the "lib" are only getting ES6 which may result in runtime errors, unless the consumer itself transpiles the code to CJS.
=> Either transpile this complete application before publishing to npm (a
.npmignore
has to be implemented, as well as aprepublish
command) OR Extract the parser from both the projects and create a third one which only publishes the parser to NPM. @jschirrmacher wdyt?