[v1] Working with third-party dependencies #129
By default, ng-packagr brings a configuration that works well with Angular and RxJS packages. However, other third-party libraries need custom configuration. Users have encountered several issues. There are also different use cases for working with third parties. This issue tries to keep an overview of those issues.
Please keep posting issues for individual / specific questions.
Use Cases for Third-Party Libraries
How should external dependencies be handled in package.json
#135 asks how external dependencies of an Angular library should be handled in
Configuring lib.externals in ng-package.json
#119 asks how to configure the
#108 is a RxJS-specific custom addition to
#230 shows how to configure with firebase
#290 asks how moment.js can be used with the
#163 asks how to configure
TypeScript import paths
In the discussion of #117, an issue with deep import paths is described because VSCode auto-suggests the deep import path (from source file structure).
Regression for embedding a global-scoped third-party library in ng-packagr 1.2.0
In PR #121, generic support for
#62 asks for generic commonjs support
The text was updated successfully, but these errors were encountered: