Replies: 1 comment
-
I noticed that, once a In order to make this work though, the "top most" project needs such a configuration as well, even if it is defined without any specific options. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey everyone 👋
I have the following scenario: My
build
target provides an additionalprod
configuration, which will run a production build of my project. So far so good: I can run this target usingnx run app:build:prod
.I added a second target
package
, which depends on thebuild
command:Also this works perfectly:
nx run app:package
runs mybuild
followed by thepackage
target; Except thatbuild
is executed using its default configuration instead ofprod
.I tried a few things like changing the target dependency to
{ "target": "build:prod", "projects": "self" }
or passing the configuration via CLI (which fails obviously;package
does not have aprod
configuration ¯_(ツ)_/¯)... With no success so far.How can I explicitly define the configuration for a target dependency?
Beta Was this translation helpful? Give feedback.
All reactions