qrious
qrious copied to clipboard
neocotic
Monorepo
I know that I just split out the code into multiple modules and repositories in #53, however, it's already becoming challenging for maintaining versioning and collaboration. While we still only have a few modules, I'd like to take the opportunity to converge into a monorepo. That way, I can perhaps ignore the loss of git history (which I already did accidentally in the initial split 😞).
I'll be looking at using something like Lerna to make it easier to publish etc. I was waiting for it to be adopted more and thoroughly tested, and babel has been using it for some time now. The packages will remain the same, they'll just all fall under this repository (again).
This should not involve a breaking change so can be done in a minor release. I'll add more info to this issue as my investigation begins.
This is going to happen. I made my first monorepo using Lerna for another project that converts SVGs to other formats and it works brilliantly. It will make publishing and maintenance much easier with a single repository.
You can avoid loss of git history by taking commits from the separate repos into the monorepo using git filter-branch.
@gyst Thanks, I'll keep that in mind. I believe Lerna has a command for cleanly importing external repos as new packages.
@neocotic Is this library still under maintenance? It has been two years since last release.
