Use the Angular Package Format
See original GitHub issueThere’s been some development in publishing libraries since our build system was last time revised. We now have an official document called Angular Package Format (APF), which describes the what and why.
As for how… There’s been a lot of discussion everywhere. In the CLI repo, it started here and after more than a year continued here. Here, we have a very informant comment by Rob, which explains problems with packaging and why CLI cannot do it the way we create apps with it.
The important bit in the comment is angular-quickstart-lib
repo by Filipe, Angular CLI core member which serves as an APF starter. There’s a PR to make the readme of that repo an official Angular guide, but looks like it got stalled for a month now; so I’m not sure where we’re at from the standpoint of “this is official and this is how it should be done” by the Angular core team.
There’s also an ongoing attempt to create a CLI for creating libraries in APF, called ng-packagr
, but it’s rather new and not used much yet. So I’d rather use the aforementioned APF boilerplate as a reference point and re-organize the repo.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:10 (4 by maintainers)
Top GitHub Comments
@lazarljubenovic no, this should be independent from the code changes, as we have to change the structure of the package content but not the source code itself.
Hey, any update on this?