Angular-cli: provide blueprint for component library as a feature

Created on 5 Jul 2016 · 8Comments · Source: angular/angular-cli

Using angular-cli improve development but something i was missing is a blueprint to create component libraries. Right now i have developed a library of services to be consumed by more than one application and i have to resort to use a yeoman generator. The generator was fine (except for the lack of testing infrastructure) but i prefer a consistent coding style and the best practices that can bring to the table the angular-cli. Any idea if this feature will be included in the roadmap? May be implementing the App Creation Using Template story is the way to achieve this.

2 (required) feature

Source

yeiniel

👍6

Most helpful comment

Hey @filipesilva i think you make a mistake marking this as a dupe of #1284 because this is the issue #1284. Is the issue number wrong?

yeiniel on 22 Sep 2016

😄2

All 8 comments

This feature is on roadmap but I have no set date for it.

filipesilva on 28 Jul 2016

Ok, but may be have you any advice how to create components/services libraries for angular2 or some manual steps for creating these ones through angular cli?

I tried to create simple library through angular cli (https://github.com/kartzum/color-generators) but got some problems. There are some:

'app' name can not be changed
after 'npm publish' package does not contain 'dist' folder without manual steps

kartzum on 9 Aug 2016

👍1

I'd like to throw in support for this issue. I have feature teams working vertical slices of the app and it would be great if I could pull those out into separate projects and still use the cli tool!