Is it possible to publish a package including its dependencies?

Type of Issue

[ ] Bug Report
[x ] Feature Request / Question

Description

_feature/question: Is it possible to package an publish a library A that depends on library B, without publishing library B?

We have a common (internal) library that is to be shared among teams. We are now making a new library/component external use, that depends on this common library. We wish to package and publish this new component without having to publish our common library as a peerDependency.

All attempts until now result in a package that is missing the code from our common library.

Is this possible?

I currently get the following error when using my package: ERROR in : ‘my-common-component’ is not a known element:

1. If ‘my-common-component’ is an Angular component, then verify that it is part of this module.
2. If ‘my-common-component’ is a Web Component then add ‘CUSTOM_ELEMENTS_SCHEMA’ to the ‘@NgModule.schemas’ of this component to suppress this message. ("

   mstviewer works! [ERROR ->]<my-common-component></my-common-component>

")

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr:  newest versieon 
@angular/*: 5.x

Please include all version numbers that might be relevant, e.g. third-party libraries

[raphael22]

“bundledDependencies” is not a viable solution for my problem. I need my final umd bundle to be embed with it’s dependencies (except for peerDependencies) in order to be used on the fly on a deployed angular application.

[github-actions[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. _{This action has been performed automatically by a bot.}