Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[next] Deprecating DefinitelyTyped types for next #37299

Closed
4 tasks done
resir014 opened this issue Aug 1, 2019 · 0 comments · Fixed by #40235
Closed
4 tasks done

[next] Deprecating DefinitelyTyped types for next #37299

resir014 opened this issue Aug 1, 2019 · 0 comments · Fixed by #40235

Comments

@resir014
Copy link
Contributor

resir014 commented Aug 1, 2019

If you know how to fix the issue, make a pull request instead.

If you do not mention the authors the issue will be ignored.


So Next.js 9 is released, and since they have migrated their core codebase to TypeScript, they have now also shipped built-in typings as of this version. So as of next@9.0.0, we will no longer have to install @types/next.

So from now on, the course of actions to take will be as follows:

  • Merge in maintenance fixes into @types/next@8 when necessary.
  • Deprecate the DefinitelyTyped typings, which will close this issue (follow these instructions)
  • Further updates/fixes to the typings shall be made to the upstream Next.js repo

@Dru89 @brikou @jthegedus @scottdj92 @joaovieira @ajliv Our work here is done! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant