Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: make sure we fully comply with the Angular Package Format (APF) #73

Closed
2 of 5 tasks
dsebastien opened this issue Mar 1, 2018 · 1 comment
Closed
2 of 5 tasks
Labels
comp: build-main Main build comp: stark-all To apply for all Stark modules comp: testing must

Comments

@dsebastien
Copy link
Contributor

dsebastien commented Mar 1, 2018

cfr Angular package format (APF): https://docs.google.com/document/d/1CZC2rcpxffTDfRDs6p1cfbmKNLA6x5O-NtkJglDaBVs/preview

Things to do we've identified so far:

@dsebastien dsebastien added comp: build-main Main build comp: stark-all To apply for all Stark modules labels Mar 1, 2018
@dsebastien dsebastien added this to the 10.0.0-alpha.1 milestone Mar 1, 2018
@dsebastien dsebastien changed the title build: make sure we support secondary entry points build: make sure we fully comply with the Angular Package Format (APF) Mar 2, 2018
@ncedric ncedric self-assigned this Mar 5, 2018
@ncedric
Copy link
Contributor

ncedric commented Mar 8, 2018

Done

@ncedric ncedric closed this as completed Mar 8, 2018
SuperITMan pushed a commit that referenced this issue Mar 8, 2018
@dsebastien dsebastien removed the P1 label Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp: build-main Main build comp: stark-all To apply for all Stark modules comp: testing must
Projects
None yet
Development

No branches or pull requests

2 participants