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
A workspace with projects with different builders will not be able to use ng test (no overrides).
The log given by the failure
The following Error is thrown:
Jasons-MacBook-Pro:oldnxws jason$ yarn test
yarn run v1.9.4
$ ng test
Architect commands with command line overrides cannot target different builders. The 'test' target would run on projectsapp1,app2 which have the following builders: @angular-devkit/build-angular:karma @nrwl/builders:jest
Error: Architect commands with command line overrides cannot target different builders. The 'test' target would run on projects app1,app2 which have the following builders: @angular-devkit/build-angular:karma @nrwl/builders:jest
at TestCommand.validate (/Users/jason/projects/temp/oldnxws/node_modules/@angular/cli/models/architect-command.js:95:27)
at Object.<anonymous> (/Users/jason/projects/temp/oldnxws/node_modules/@angular/cli/models/command-runner.js:175:39)
at Generator.next (<anonymous>)
at fulfilled (/Users/jason/projects/temp/oldnxws/node_modules/@angular/cli/models/command-runner.js:11:58)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3
Desired functionality
I understand that with different builders, sending overrides to all of them will be virtually impossible to manage. However, without overrides should not be an error (ng test with no overrides) since the configuration within angular.json will be specific to the builder for each target.
Mention any other details that might be useful
This would be extremely useful for something I'm working on for Nx which is to build backends inside an angular cli workspace. If ng test (no overrides) were to test all projects regardless of which builder they were using, just that they have a test target.
Also might be useful
Also, if there could be a flag that allows overrides to be sent, it could enable some usage if two builders were to share similar options.
The text was updated successfully, but these errors were encountered:
Bug Report or Feature Request (mark with an
x
)Command (mark with an
x
)Versions
Repro steps
A workspace with projects with different builders will not be able to use
ng test
(no overrides).The log given by the failure
The following Error is thrown:
Desired functionality
I understand that with different builders, sending overrides to all of them will be virtually impossible to manage. However, without overrides should not be an error (
ng test
with no overrides) since the configuration withinangular.json
will be specific to the builder for each target.Mention any other details that might be useful
This would be extremely useful for something I'm working on for Nx which is to build backends inside an angular cli workspace. If
ng test
(no overrides) were to test all projects regardless of which builder they were using, just that they have atest
target.Also might be useful
Also, if there could be a flag that allows overrides to be sent, it could enable some usage if two builders were to share similar options.
The text was updated successfully, but these errors were encountered: