migrate towards using a monorepo: ES6/rollup/etc. is a horror otherwise #16
Comments
GerHobbelt
added a commit
that referenced
this issue
Oct 15, 2017
…r where we can work on making the monorepo a reality.
|
Done. (Well.... sort of. The subpackages are still a hassle to publish but at least jison itself is now produced much more easily and with no risk of screwing up the rebuild process. |
GerHobbelt
added a commit
that referenced
this issue
Oct 24, 2017
…ib, ebnf-parser, lex-parser, jison-lex, jison2json, json2jison); those remain as npm packages, produced from this *monorepo* (#16)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See also: https://github.com/GerHobbelt/jison/projects/3
Now that I am upgrading jison et al to produce ES6/ES2015 compatible output and be ES6/ES2015 itself (at least as far as modules' import/export is concerned), the split into submodules proves to be a real horror as it is NOT a dependency tree but rather a (cyclic!) dependency graph at development time.
In short: 💀 💢 😭 👿 👎 👎 👎
The text was updated successfully, but these errors were encountered: