Skip to content
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

Clarify interaction between --node-env and mode #7080

Closed
wants to merge 1 commit into from

Commits on Dec 15, 2023

  1. Clarify interaction between --node-env and mode

    The interpretation of the current description is ambiguous, as it pertains to how a configuration function can or cannot benefit from the use of `--node-env` as a way to set `mode`. One might interpret it as if that happens before the configuration function is invoked, and therefore should be available to use for logic like switching in the function. That would be wrong. This update makes it clear that the assignment of a default `mode` based on `--node-env` happens after the configuration function is executed.
    
    Related: webpack#4009 
    
    Fixes webpack#3992
    aoberoi authored Dec 15, 2023
    Configuration menu
    Copy the full SHA
    d00cbec View commit details
    Browse the repository at this point in the history