History

fix(webpack): apply-base-config should initialize options it will set #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

2024-05-14 14:19:47 +01:00

docs

feat(misc): v19 cleanup for Nx plugins (#23104 )

2024-05-02 13:37:12 -04:00

src

fix(webpack): apply-base-config should initialize options it will set #23296 (#23368 )

2024-05-14 14:19:47 +01:00

.eslintrc.json

fix(angular): ajv hoisting issue (#21641 )

2024-02-06 21:21:12 +04:00

app-plugin.ts

feat(webpack): change plugin import paths to speed up config loading (#23021 )