Skip to content

fix(vite): set NODE_ENV to production correctly #28584#28663

Merged
Coly010 merged 1 commit intomasterfrom
vite/fix-node-env
Oct 28, 2024
Merged

fix(vite): set NODE_ENV to production correctly #28584#28663
Coly010 merged 1 commit intomasterfrom
vite/fix-node-env

Conversation

@Coly010
Copy link
Copy Markdown
Contributor

@Coly010 Coly010 commented Oct 28, 2024

Current Behavior

After the switch to use resolveConfig we failed to set the value for NODE_ENV which is an argument to the function.
This means it always defaulted to development.

Expected Behavior

Ensure NODE_ENV is set as expected.

Related Issue(s)

Fixes #28584

@Coly010 Coly010 requested a review from a team as a code owner October 28, 2024 11:59
@Coly010 Coly010 requested a review from mandarini October 28, 2024 11:59
@Coly010 Coly010 self-assigned this Oct 28, 2024
@vercel
Copy link
Copy Markdown

vercel Bot commented Oct 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Oct 28, 2024 0:03am

@nx-cloud
Copy link
Copy Markdown
Contributor

nx-cloud Bot commented Oct 28, 2024

@Coly010 Coly010 merged commit 0857492 into master Oct 28, 2024
@Coly010 Coly010 deleted the vite/fix-node-env branch October 28, 2024 13:43
@Coly010 Coly010 mentioned this pull request Oct 28, 2024
4 tasks
jaysoo pushed a commit that referenced this pull request Oct 31, 2024
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->
After the switch to use `resolveConfig` we failed to set the value for
`NODE_ENV` which is an argument to the function.
This means it always defaulted to development.


## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
Ensure `NODE_ENV` is set as expected.

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #28584
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Nov 3, 2024

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.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Nov 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NODE_ENV=development in production (vite:build)

2 participants