Currently I'm working with the following versions:
typescript --> 2.6.2
angular --> 5.2.1
@angular/cli --> 1.6.5
After packaging my own library with some components using ng-packagr ("ng-packagr": "^1.6.0"), I added the files created on my…
Here's a repo that reproduces it: https://github.com/dragonflypl/ng-packagr-issue
I've create a simple package logging. npm run build generates the library + does npm pack
Then I generated fooGui with Angular CLI and installed library it via npm…
I built an Angular application [MASTER]. Inside of it, I would like to import another application built with a feature module [FEATURE_MODULE].
To generate the FEATURE_MODULE, I followed this tutorial: Modules tutorial. This exports a feature module…
I have an issue with inject service dynamically.
// NPM Package 1:
@Injectable()
export abstract class BaseService { ... }
@Injectable()
export class ServiceA extends BaseService { ... }
@Injectable()
export class ServiceB extends BaseService { ...…
I'm building an Angular library with ng-packagr.
When serving my app with the packed library used, I get this warning:
. Furthermore, when serving the app, I get this errormessage:
core_1 is imported alongside other modules in the top:
import…
I have an Angular 13 library on the go. It works with the other modules I have already got in there, but this new module I'm moving into place uses material, and it's not happy.
The new module itself is fine and builds until I make any kind of use…
We have a library project that lives in an nx project that we publish to npmjs. It's a collection of components derived from @angular/material. The library is published to npmjs @vdlx/vdl-angular.
Our build uses ng-packagr to build each of the…