Fix import type/typeof printing with no specifiers
#14309
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/51374/ |
nicolo-ribaudo
added
the
PR: Bug Fix 🐛
nicolo-ribaudo
changed the title
import type/typeof printing with no specifiers
nicolo-ribaudo
force-pushed
the
empty-specifiers-bug
branch
from
db31329
to
4fd02b8
Compare
nicolo-ribaudo
approved these changes
Feb 27, 2022
existentialism
approved these changes
Feb 28, 2022
github-actions
bot
added
the
outdated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Empty braces will still be printed even if the there are no specifers, check added for importKind, empty braces will be printed on type and typeof imports.