Skip to content

repository configuration improvements #2447

Open
@dsl400

Description

@dsl400

Is your feature request related to a problem? Please describe.

From angular perspective the development environment could use some refinements.

My understanding of monorepo is "only one node_modules folder" but I am not really sure this can apply here. However configuring the output of the build in such a manner that does not include the node_modules folder can be done.

For debugging purposes I had to link the angular packages (angular, angular-material, core), this caused the build of my project to fail.

It took me a wile to figure out that the problem was caused by the node_modules folder existing in every package ( angular/node_modules, angular-material/node_modules, core/node_modules).

The sole purpose of the link is to have quick access to the latest modification but this was not the case, because I removed the node_modules folders now the packages failed to build

The whole test cycle got very complex. What could have been a "modify > save > wait" turned into a long and annoying list of steps that waste a lot of time.

Describe the solution you'd like

An improved repo configuration.

Describe alternatives you've considered

Package

all angular packages

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions