fix: Clone options object before mutating it #225
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.
This fixes a weird stateful bug where a single comment-based JSX pragma declaration can change the pragma used for all subsequent transforms.
The issue is caused by the options object being mutated by the
transform()
function. In particular, it is done when a@jsx
directive comment is found in a file. If you then re-use the same options object instance for your next transform call (which coincidentally is what is done bybuble-loader
), you will be potentially passing through an incorrect JSX pragma.Example
The solution I have implemented here is to shallow-clone the options object before mutating it.