Getting error to build application after upgrade to the version 11.1.2

[aaschlote]

Hello all,

I'm getting the follow error below after I upgraded the next js version to 11.1.2. I'm current using the version 17.0.19 of the @types/react.

Someone is also facing it? Do we have a solution?

On the version 11.1.0 the error doesn't happens.

Best
Alex Schlote

[thibautsabot]

Hello !

It's probably because of this PR #28269 which was part of the https://github.com/vercel/next.js/releases/tag/v11.1.1.

Do you have a custom component that wraps the next/image ?

[aaschlote]

it worked fine, thank you very much.

Do you think I should open an issue? Because it wasn't happening before.

[thibautsabot]

Pinging @styfle, maybe he wants to be aware of this interaction with the React types 🙂

[styfle]

I'll remove that TS type since it wasn't necessary #28672

[styfle]

This is fixed in v11.1.3-canary.0.

You can try it out today with yarn add next@canary

[aaschlote]

I couldn't install it, I had some issues with the sentry/nextjs dependency

`While resolving: @sentry/nextjs@6.11.0
Found: next@11.1.3-canary.0
node_modules/next
next@"11.1.3-canary.0" from the root project

Could not resolve dependency:
peer next@"^10.0.8 || ^11.0" from @sentry/nextjs@6.11.0
node_modules/@sentry/nextjs
@sentry/nextjs@"6.11.0" from the root project

Conflicting peer dependency: next@11.1.2
node_modules/next
peer next@"^10.0.8 || ^11.0" from @sentry/nextjs@6.11.0
node_modules/@sentry/nextjs
@sentry/nextjs@"6.11.0" from the root project`

[balazsorban44]

Having the same issue, looks like it was introduced here:
https://github.com/vercel/next.js/pull/28269/files#diff-f1cccfe490138be7dae0d63562f6a2834af92d21130e0ff10d6de7ad30613f6b

[aaschlote]

do you know when it will be the official release for this fix?

[balazsorban44]

You can install any version 11.1.3-canary.0 or above, and the error goes away 😄.

If you mean when will it hit a stable release not canary, I don't know. 🤷

[aaschlote]

@balazsorban44 Thank you for your message, I mean the stable release, I wouldn't bring the canary release to production. I'll wait for it.

[drbalm]

Seeing this as well upon upgrading to v11.1.3. Looks like the fix wasn't included in the v11.1.3 patch? https://github.com/vercel/next.js/blob/v11.1.3/packages/next/types/index.d.ts#L45 Any updates as to when this is going to be available?

[thibautsabot]

There weren't any stable 11.1.3 version.

You will need to either upgrade to v12 or use a canary version.