refactor!: remove next/*.js
exports
#647
Merged
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 one is added to help hi-ogawa/next-learn#1 (weird import by nextauth?) but it's fairly ugly (probably it confused IDE import completion too?) so let's forget about it and remove them.
Probably users can workaround it by doing
alias
manually.I wonder what Next.js would end up eventually
exports
topackage.json
vercel/next.js#68455Well, it looks like next-auth has fixed it already
next/*.js
nextauthjs/next-auth#11551