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
add module argument to DefinePlugin.runtimeValue functions #8306
Conversation
PR webpack#6793 added the ability for DefinePlugin to use function that return values. This PR just add the ability to these functions to access the module being parsed (see webpack#8301). eg. ``` webpack.DefinePlugin.runtimeValue(module => module.resource ....) ```
For maintainers only:
|
c71b36a
to
2b0025a
Compare
current test is |
Co-Authored-By: FranckFreiburger <FranckFreiburger@users.noreply.github.com>
@FranckFreiburger Thanks for your update. I labeled the Pull Request so reviewers will review it again. @sokra Please review the new changes. |
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Just a little hint from a friendly bot about the best practice when submitting pull requests:
You don't have to change it for this PR, just make sure to follow this hint the next time you submit a PR. |
Thanks |
PR #6793 added the ability for DefinePlugin to use function that return values.
This PR just add the ability to these functions to access the module being parsed (see #8301).
eg.
issue #8301
What kind of change does this PR introduce?
It adds a
module
an argument to fct in DefinePlugin.runtimeValue(fct)Did you add tests for your changes?
yes
Does this PR introduce a breaking change?
no
What needs to be documented once your changes are merged?
About the additional
module
argument