Removal of --define-process-env-node-env is undocumented.
#4360
Labels
Comments
junhaoliao
changed the title
--define-process-env-node-env is undocumented--define-process-env-node-env is undocumented.
|
this is replaced by |
Thank you for pointing that out. I did notice this change after looking through a few Pull Requests, and it did cause some confusion since it wasn't clearly documented in the new major version release notes. Do you consider the proposed changes in #4361 adequately address this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The --define-process-env-node-env option is still mentioned in the README.md, even though it seems to have been renamed as
config-node-envin #4318 . This could lead to confusion among users trying to use the option.What is the current behavior?
The README.md references the --define-process-env-node-env option, which appears to no longer exist or function as expected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The README.md should accurately reflect the current state of the webpack-cli options. If --define-process-env-node-env has been removed, it should be documented accordingly, and references to it should be removed or updated.
Screenshots
N/A
Please paste the results of
npx webpack-cli infohere, and mention other relevant informationAdditional context
This issue is about keeping the documentation in sync with the actual functionality of webpack-cli. The outdated mention of --define-process-env-node-env can mislead users.
The text was updated successfully, but these errors were encountered: