Question: Mono repo?

[Rayraegah]

Will you consider turning Sur+ into a mono repo with something like Lerna?

Happy to help.

[adamhaile]

Hi Ray --
Sorry for the slow reply. Yeah, I would find something like that useful. It would have helped a lot, I think, when I was getting coordinated beta releases of the various packages out. But I don't really know what best practices are here, and I also don't know how big to make the scope of the mono repo. I think I'd leave S out of it, as it has utility beyond surplus, but again I don't have experience in how inclusive a mono repo should be. At a minimum, surplus plus the various build tools (surplus-loader, etc) makes sense. Any advice?
-- Adam

[Rayraegah]

Yes. Its more about modularity and convenience.

Let me see if i can make it simple for you: if the project is called Surplus then the mono repo has:

/packages/surplus
/packages/babel-preset-surplus
/packages/surplus-*

There are no best practices afaik, but what we usually do is keep dependencies together in /packages/ dir. For packages you don't intent to publish keep them in /packages/ dir but mark them as private: true in package.json

In the case of S, you could simply have S as a git submodule inside /packages/ (I do this a lot, although its shunned upon)

Here are a few mono repo samples
https://github.com/egoist/poi (pure)
https://github.com/vuejs/vue (impure)