Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Publish npm #84
This was referenced
May 6, 2017
@iamcal have you considered merging all of these projects into a monorepo? The benefits that you may see would be:
I know you've mentioned in the past that you don't use npm, so I can imagine how it might be frustrating to have to manage all of these different packages if there are many steps to doing a release. If you think that could be the case, then a monorepo could be worth looking into. If you've got some other plan to automate it, or don't think the work will be too much, then no worries.
I really appreciate that you're doing this, by the way! Thank you!
I assume you mean this repo and the JS one? There are about 10 different language versions which rely on this datasource, only some of which are by me, so I don't have the option to merge.
Beyond that, the problems with publishing to npm are:
I'm close to having one base package on npm (with minimal images), plus one per image set which contains everything. If I can get around the stack overflow problems, it'll be done.