fix(node): ensure cwd is set in target correctly #31864
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
View your CI Pipeline Execution ↗ for commit ea6e258
☁️ Nx Cloud last updated this comment at |
|
Hey @creadicted, thanks for the PR can you fix the formatting Other than that the changes look good to be merged. |
creadicted
force-pushed
the
31863-nest-webpack-args
branch
from
f8844fe to
ea6e258
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
The Nest.js webpack build target configuration was generating webpack-cli arguments without the required cwd in build.options.
Expected Behavior
The Nest.js webpack build target should generate proper webpack-cli arguments with the cwd as part of the build.options
Related Issue(s)
Fixes #31863