You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the --all (or --projects) option for the ng build schematic. This option would build libraries, then applications, then the default project; because of how they are dependent of each other. It should ignore the e2e projects.
To make it easier to find, and order which project should be built first, it would be better to change the generate schematics of application and library to change the angular.json file adding libraries and applications as attributes holding an array of strings.
Building several libraries and applications in a monorepo that all packages/projects have the same semantic version.
When working with several libraries and applications on a monorepo, it is a pain to create a npm script for each project, and update the build:all npm script. Running a single command to build all projects is less painfull and has less chance of mistakes (forgetting, skipping).
Example / attempt
As much as this example works for me, I still can't order the libraries and applications. If I have a library that needs another, and it builds first, it would break.
Feature requested
Add the
--all
(or--projects
) option for theng build
schematic. This option would build libraries, then applications, then the default project; because of how they are dependent of each other. It should ignore the e2e projects.To make it easier to find, and order which project should be built first, it would be better to change the generate schematics of
application
andlibrary
to change the angular.json file addinglibraries
andapplications
as attributes holding an array of strings.Case of use
Building several libraries and applications in a monorepo that all packages/projects have the same semantic version.
When working with several libraries and applications on a monorepo, it is a pain to create a npm script for each project, and update the
build:all
npm script. Running a single command to build all projects is less painfull and has less chance of mistakes (forgetting, skipping).Example / attempt
As much as this example works for me, I still can't order the libraries and applications. If I have a library that needs another, and it builds first, it would break.
The text was updated successfully, but these errors were encountered: