Add Next.js 12 support, update tests #10
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Next.js 12 requires another set of changes in order to keep this plugin working. Just like I did with Next.js 11 support, I added the necessary code to make it work again, and updated/added test cases to cover the new logic.
In order to make Next.js 12 actually use the Babel loader instead of its new default SWC loader, it may be required to add an empty
.babelrcfile to your Next.js root directory. I added a check and an error message for this scenario, too, so that users of this plugin will know what to do if Next.js isn't using Babel at all.