My Meteor project has become a big monolith, so for (mostly) performance and healthiness reasons I’m considering splitting it up into several packages.
I’d like to have separate meteor instances accessing the same DB, but doing their own specific thing (admin, client type 1, client type 2, for example).
So the “core” I would need everywhere includes DB simple-schemas, proprietary JS functions, some config/theming options, a few generic front-end components and meteor methods (server-only and server-client).
How would you approach something like this:
- private npm modules?
- atmosphere packages?
- git submodules?
Especially considering server/client separation in a meteor app, this has proven to be a bit trickier than I thought. Also how does meteor minify/strip external modules? Can you use server/client folders?
Any tips are appreciated