Upgrade the CLI and Use CLI Packager instead of ng-packagr.
Sure I'll have a look :)
I did some tests yesterday with a new project and it seems to work pretty well
@leon one thing I did find out is that the current rc for the cli doesn't work with AOT while serving the app (which is something we do now) not a deal breaker just needs to be kept in mind
Took it for a spin, not working if lib1 depends on lib2 ... doesn't support scope yet (@scope/package). Now that they have released 6.0.0, you may want to take it for a spin and see if with the minimal tweak, you can make it work ngxs.
@un33k yeah you would have to do a setup kinda like what we have here where you define the tsconfig paths. just need to make sure that ng-packagr is given a custom tsconfig
@deebloo I did pass custom tsconfig with lots of combinations/permissions with no luck. There are open bugs against the @scope/pkg support. It would be nice to skip npm link. I am sure the CLI folks are working hard to add support or docs. I think they had to rush an incomplete release to align themselves with ng 6. It would be great if you find a way to make it work.
on issues so far. using angular-cli 6.0.1
https://github.com/xmlking/ngx-filepond
We now updated to last version ng-packagr
Most helpful comment
Sure I'll have a look :)