refactor: process_js_with_custom_pass should accept comments as paramter #6290
+51
−18
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.
Description:
process_js_with_custom_pass()
should acceptcomments
as parameter instead of using it internally, as user may pass an already parsed AST, and parse also needcomments
as parameter, so thosecomments
should be the same.Breaking Change
It's a breaking change, and I remember that next.js is using this API.
Also bindings/binding_core_wasm is using too.
Do I need to edit CHANGELOG, or if it can be done by
swc-bot