-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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): apply-base-config should initialize options it will set #23296 #23368
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 4d13625. 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. |
Thank you @Coly010! 🙌 |
…23296 (#23368) <!-- 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` --> ## Current Behavior <!-- This is the behavior we have today --> The `@nx/webpack/plugin` will resolve and read webpack options from user defined config files. However, it does not set the env vars indicating that a task is being run, because tasks are not being run at this stage. This means that certain config properties are not being set by `applyBaseConfig`. Users' webpack configs may rely on these properties being set so they can modify them. When not set, this throws, meaning the graph cannot be constructed. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Initialize the properties that we usually set when `applyBaseConfig` is used. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #23296 (cherry picked from commit 3e84967)
…23296 (#23368) <!-- 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` --> ## Current Behavior <!-- This is the behavior we have today --> The `@nx/webpack/plugin` will resolve and read webpack options from user defined config files. However, it does not set the env vars indicating that a task is being run, because tasks are not being run at this stage. This means that certain config properties are not being set by `applyBaseConfig`. Users' webpack configs may rely on these properties being set so they can modify them. When not set, this throws, meaning the graph cannot be constructed. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Initialize the properties that we usually set when `applyBaseConfig` is used. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #23296
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. |
Current Behavior
The
@nx/webpack/plugin
will resolve and read webpack options from user defined config files.However, it does not set the env vars indicating that a task is being run, because tasks are not being run at this stage.
This means that certain config properties are not being set by
applyBaseConfig
.Users' webpack configs may rely on these properties being set so they can modify them.
When not set, this throws, meaning the graph cannot be constructed.
Expected Behavior
Initialize the properties that we usually set when
applyBaseConfig
is used.Related Issue(s)
Fixes #23296