Skip to content

feature: support multiple "apps" into a single angular-cli.json file #3629

Closed

Description

@alexandrehebert

Hi,

I wanted to know if you planned to introduce the support for multiple projects into one single angular-cli.json file (as the current angular-cli.json file structure suggest it, with an array type for the "apps" configuration).

The expected behavior would be to produce multiple Angular2 applications (different JS files) by running a single ng build command from the project root folder.

Regards,
Alex.

Activity

  1. changed the title [-]feature: support for multiple "apps" into a single angular-cli.json file[/-] [+]feature: support multiple "apps" into a single angular-cli.json file[/+] on Dec 19, 2016
  2. Destreyf commented on Dec 19, 2016

    @Destreyf

    @alexandrehebert This has been brought up in the past, i have a small solution that i wrote up as an attempt to test this concept, the angular-cli only processes the first angular-cli.json app entry, so you can use a small node.js (could even be gulp) script to swap their orders, here's a link to that issue.

    My Comment

    Issue: #3213

  3. alexandrehebert commented on Dec 22, 2016

    @alexandrehebert
    Author

    Thanks a lot for your answer, closing this issue and lets continue this conversation in the #3213 feed.

  4. leocaseiro commented on Apr 4, 2017

    @leocaseiro

    Check #5737

  5. shoagraw commented on Apr 6, 2017

    @shoagraw

    This is really awesome, if you wand detailed pls check here also.
    https://yakovfain.com/2017/04/06/angular-cli-multiple-apps-in-the-same-project/

  6. delpast1 commented on Jun 6, 2017

    @delpast1
  7. bresleveloper commented on Mar 14, 2018

    @bresleveloper

    @delpast1 hi i follows it and it worked, try again step by step carefully

  8. angular-automatic-lock-bot commented on Sep 8, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  9. locked and limited conversation to collaborators on Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions