Skip to content

Bundling Third-Party Dependencies In Library #9

Description

@collindutter

Thanks for the very useful repo! We're running into one issue though.

Is there a way we can configure this so that the base application doesn't need to know about the library's third-party dependencies? In this example, Clarity is installed in the base application, but is there a way to provide it in the library instead?

Following this issue ng-packagr/ng-packagr#1231 I've gotten the library bundle to include the third party dependency, but I can't seem to load it in the base application.

Any suggestions?
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions