CODEWITHSUNDEEP
angulargitnpm
Su4p
Su4p

Reputation: 865

how to maintain angular modules after splitting and publish on npm

I'm working on an angular app. In order to reuse and avoid copy pasting most of the components and services in an other app. I splited the app into modules and published them on a private npm and git server.

Now that's all done I'm wondering how to work on those modules. I face multiple issues regarding this point. First they can't work by themself most of them require strong authentification and permission in order to get datas. Each module is now on a git repo.

Should I create a meta project without source versioning using those versionned modules without npm install ?

Upvotes: 0

Views: 198

Answers (1)

Shai Reznik - HiRez.io
Shai Reznik - HiRez.io

Reputation: 8948

Sounds like you can benefit from having a monorepo.

Have you tried checking - Nrwl Extensions ?

They built a solution for just that - sharing the same modules with different apps.

The difference is, is that they're all in one git repository, but you can still publish everything as different npm packages.

Upvotes: 1

Related Questions