Skip to content

Split angular.json into multiple files聽#22655

Open
Enhancement
Open
Split angular.json into multiple files#22655
Enhancement
Labels
area: @angular-devkit/corearea: @angular/clifeatureLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under consideration
Milestone
needsTriage

Description

@developer239
developer239
opened on Feb 6, 2022

馃殌 Feature request

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Description

I have a monorepository and I want to split my angular.json into separate files.

So that I can have something like this:

{
  "version": 2,
  "projects": {
    "module-auth": "packages/auth",
    "module-core": "packages/core",
    "module-button": "packages/button"
  }
}

After working with NX I noticed that with Lerna and the usual setup my angular.json file has 119 lines of code even though I basically have an empty repository. I believe that having a single angular.json file is a very bad idea, especially for bigger monorepositories or UI libraries.

Describe the solution you'd like

Make the JSON configuration 1:1 with what NX does or implement similar functionality.

Activity

  1. alan-agius4
    changed the title [-]Is there going to be Angular Json V2?[/-] [+]Split angular.json into multiple files[/+] on Feb 7, 2022

  2. alan-agius4 commented on Feb 7, 2022

    @alan-agius4
    alan-agius4
    on Feb 7, 2022
    Collaborator

    Splitting angular.json into multiple projects level configuration is something that we definitly want to explore in the future.

    However, it is very unlikely that it will 1:1 with the NX solution.

  3. alan-agius4
    added
    area: @angular/cli
    area: @angular-devkit/core
    on Feb 7, 2022
  4. ngbot
    modified the milestone: needsTriage on Feb 7, 2022
  5. alan-agius4
    added
    featureLabel used to distinguish feature request from other issues
    on Feb 7, 2022
  6. alan-agius4
    changed the title [-]Split angular.json into multiple files[/-] [+]Split `angular.json` into multiple files[/+] on Feb 8, 2022
  7. angular-robot
    added
    feature: votes requiredFeature request which is currently still in the voting phase
    on Feb 8, 2022

  8. angular-robot commented on Feb 8, 2022

    @angular-robot
    angular-robotbot
    on Feb 8, 2022
    Contributor

    This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

    You can find more details about the feature request process in our documentation.

  9. Den-dp commented on Feb 17, 2022

    @Den-dp
    Den-dp
    on Feb 17, 2022

    I think that such functionality will lead to a win-win situation for both Angular and Nx.

    • ng cli users will get more intuitive and fast code locating
    • nx cli team will get an opportunity to adopt the new native approach of splitting angular.json (and remove some hacks related to v2 schema)

    cc: @vsavkin

  10. developer239 commented on Feb 17, 2022

    @developer239
    developer239
    on Feb 17, 2022
    Author

    @Den-dp I will share this issue with more people maybe it will get at least into the consideration list. I have no idea why would anyone dislike this and I would like to hear counterarguments. 馃槄

    Personally, if I had to work on a monorepo with Angular and without nx I would write a custom script that would build the angular.json file the way I described.

  11. angular-robot
    added
    feature: under considerationFeature request for which voting has completed and the request is now under consideration
    and removed
    feature: votes requiredFeature request which is currently still in the voting phase
    on Feb 18, 2022

  12. srukshan98 commented on Aug 9, 2024

    @srukshan98
    srukshan98
    on Aug 9, 2024

    It is essential to address this in Angular now, especially with the advent of native federation, which simplifies the process of working on microfrontends within Angular workspaces. Managing a large angular.json file in this context is neither ideal nor efficient and can become quite cumbersome.

  13. alan-agius4
    marked Allow projects to have their own angular.json file #30278 as a duplicate of this issue on May 9, 2025

  14. PowerSupply commented on May 20, 2025

    @PowerSupply
    PowerSupply
    on May 20, 2025

    Anything new regarding this?

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

    area: @angular-devkit/corearea: @angular/clifeatureLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under consideration

    Type

    Enhancement

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions