Modify custom type to imported type from next #294
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
- Fixed bug with incompatible next v9.5.5
|
Just remove the unused types. |
|
Thanks for the PR, I will do cleanup by myself. |
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.
Hi @kirill-konshin ,
I requested PR a couple of days ago. because of compatibility problem with Next.js v9.5.5+
Thank you for merge.
But announced Next.js v10 yesterday.
So need a few more types for resolve the compatibility problem.
What if there is a reason to use custom types instead of import types?
I'm having a compatibility problem.
Thank you for the quick merge and I'd like to request a quick release.