-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
feat: support sourcemap for experiments css when using eval devtool #20191
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
base: main
Are you sure you want to change the base?
Conversation
|
|
This PR is packaged and the instant preview is available (222c667). Install it locally:
npm i -D webpack@https://pkg.pr.new/webpack@222c667
yarn add -D webpack@https://pkg.pr.new/webpack@222c667
pnpm add -D webpack@https://pkg.pr.new/webpack@222c667 |
CodSpeed Performance ReportMerging #20191 will not alter performanceComparing Summary
|
alexander-akait
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's add a test cases
Another problem - we should allow to set CSS source map values by user too, like hidden-source-map and etc
So I am think about to allow devtool accepts arrays, but because we can't change devtool type for webpack@5, let's add an internal option (devtoolByTypes, maybe better name in normalization) and store source map values for types there, i.e.
devtool can be string | { test: Rule, type: "source-map" | "hidden-source-map" | "etc" }, but then in normalization we found a JS value and set it to devtool (to keep devtool a string), technically we can just take the first value of an array (but feel free to think here)
Summary
What kind of change does this PR introduce?
TODO
Did you add tests for your changes?
Yes
Does this PR introduce a breaking change?
No
If relevant, what needs to be documented once your changes are merged or what have you already documented?
devtoolandexperiments.css