Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[typescript] Broken compatibility with @types/next

See original GitHub issue

Bug report

Describe the bug

Looks like this after this change https://github.com/zeit/next.js/pull/7154/files#diff-e5f184d6408bb983da44fe3b0f27d4faR10 external types from @types/next are no longer used.

To Reproduce

git clone git@github.com:adam187/next-js-ts-error-example.git
yarn install
yarn ts:check:server

Expected behavior

Types should work properly

System information

Version of Next.js: 8.1.1-canary.12

Issue Analytics

State:
Created 4 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

Timercommented, May 14, 2019

@nhooyr you can install next@canary to try them!

2reactions

Timercommented, May 7, 2019

Hi @adam187! Unfortunately, this is unavoidable for any package transitioning from external typings to provided type declarations.

I’ll close this as unactionable – btw: we’ll likely release these changes under 8.2.0 (not 8.1.1)!

Top Results From Across the Web

[typescript] Broken compatibility with @types/next · Issue #7247

@timneutkens I agree it's not really a bug, but it can be problematic for typescript users that want to upgrade to next.js@8.1.1 and...

Documentation - TypeScript 3.9

This goal of this type operator is to accurately model the way that Promise unwrapping works in JavaScript. We initially anticipated shipping awaited...

Are typescript 3.0 type definitions backwards compatible to ts2?

I'm writing a react component library in typescript 3. How can I ensure that my generated .d.ts files are compatible with typescript 2 ......

Announcing TypeScript 4.8 - Microsoft Developer Blogs

While TypeScript strives to avoid major breaks, even small changes in the built-in libraries can cause issues. We don't expect major breaks as...

TypeScript errors and how to fix them

Be aware that this breaks the contract (signature) of the function and is ... ES5/ES3 because it does not refer to a Promise-compatible...