-
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(webpack): resolve assets from executor options as relative to workspace root #22544
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 816cfb2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
options // plugin options take precedence | ||
options, | ||
// executor options take precedence (especially for overriding with CLI args) | ||
originalTargetOptions |
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.
The order here was previously set wrong. The executor options should override plugin options, since users can pass CLI args, or have overrides in configurations
.
2dcacc4
to
816cfb2
Compare
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. |
The previous fix to relative asset paths introduced a regression when using
@nx/webpack:webpack
executor.When options are passed from the executor, the paths are relative to the workspace root not project root. Thus, we need special handling when normalizing executor options.
Current Behavior
Executor is resolving assets relative to project root.
Expected Behavior
Executor options should always be relative to workspace root for consistency.
Related Issue(s)
Fixes #