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.
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.
Since
warning
is a Rollup object that we pass back to rollup, I'd prefer if we could avoid modifying it.Instead, we can create an
osifyPath = str => str.split("/").join(path.sep)
function and dowarning.exporter === osifyPath("packages/babel-core/src/index.ts")
below ("osify" = "make it like the os").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.
That's right! We should not modify this object.
The requested change has been completed.
But it looks a bit odd that
"@babel/helper-define-polyfill-provider" -> "@babel\helper-define-polyfill-provider"
And this is a little inconvenient, we need to copy and paste
osifyPath
when adding new conditions.Maybe we can deep clone the
warning
object, which is a small object.