feat: expose webpack.target as rawTarget #943
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please Read the CONTRIBUTING Guidelines
In particular the portion on Commit Message Formatting
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
Currently the target exposed via
caller.target
is the normalized target.What is the new behavior?
This change adds a new property called
rawTarget
that exposes the original target as set on the webpack configuration.Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the following...
Other information:
In the future, I think browserlistEnv option could be automatically set when the webpack's target option is set using
browserslist:${env}
. I believe that would make the webpack / babel / browserslist integration easier.I'm afraid that would be a breaking change, and since there are, based on the documentation, future breaking changes it might make sense to wait for that to introduce this automatic
browserlistEnv
setting.