Closed chenyuanchn closed 6 years ago
I think this use case is out of the scope of this generator. You'll have to scaffold two different projects and npm link
both to your project. Might not be the best approach if you want to keep both libs in a monolithic repo. @jvandemo you got support for multiple packages in your roadmap?
@chenyuanchn — Thank you for the suggestion 👍 @caroso1222 — Thank you for your follow-up 👍
Currently, multiple libraries are indeed not officially supported. If there are more use cases for it, we can definitely consider adding it to the roadmap.
I will close this issue for now. If anyone else feels a need for a mono-repo architecture, please add your vote to this issue so we can re-open it if needed.
Thanks again!
like this: -src --lib1 ---index.ts ---package.json ---lib1.component.ts ---... --lib2 ---index.ts ---package.json ---lib2.component.ts ---...
after npm run build: -dist --lib1 ---index.d.ts ---index.js ---package.json ---... --lib2 ---index.d.ts ---index.js ---package.json ---...
That's the way I can: cd dist/lib1 npm publish cd dist/lib2 npm publish
There are two packages on NPM