fix(babel-preset,shaker): do not delete exported functions even if its body was deleted #1237
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.
Motivation
Linaria currently has a bug that leads to the deletion of exported functions from some modules when their body contains restricted code, such as JSX, React hooks, or browser API. (see #1226)
Summary
This pull request addresses the aforementioned bug by replacing the problematic functions with an empty one instead of deleting them. By doing so, we preserve the exported functions while effectively neutralizing the restricted code within them. This approach maintains the original structure of the module exports without causing any unexpected side effects or errors.