-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(node): When serving using js:node executor NODE_ENV should not be undefined #17375
fix(node): When serving using js:node executor NODE_ENV should not be undefined #17375
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
7ea09f5
to
abb39ac
Compare
… undefined closes: nrwl#16960
abb39ac
to
8cfbdd0
Compare
@@ -36,6 +36,7 @@ export async function* nodeExecutor( | |||
options: NodeExecutorOptions, | |||
context: ExecutorContext | |||
) { | |||
process.env.NODE_ENV ??= context?.configurationName ?? 'development'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these both default to the same value? Currently esbuild defaults to production and this hits dev
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is serve, I don't think we default it to production
right?
These should not be the same value.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
closes: #16960