Module not found: Can't resolve 'antd/es/ConfigProvider'

[Staefloded]

Reproduction link

https://github.com/Staefloded/antd-bug

Steps to reproduce

Wrap <Component /> with ConfigProvider

What is expected?

No error should be shown

What is actually happening?

Module not found: Can't resolve 'antd/es/ConfigProvider'

Environment	Info
antd	5.6.4
React	18.2
System	M2 MacBook Pro
Browser	Chrome

[monokaijs]

Similar here

[jkirkpatrick24]

I think this a compatibility issue with the most recent NextJS release.

If you install version 13.4.7 of next, everything works as expected, but bumping to 13.4.8 surfaces this error.

[ArvindSteamA]

Same issue here.

[Staefloded]

I think this a compatibility issue with the most recent NextJS release.

If you install version 13.4.7 of next, everything works as expected, but bumping to 13.4.8 surfaces this error.

This works
Thanks
But the issue still needs to be fixed though.

[seanmcquaid]

Same deal for me with the newest Next 13.4.8

[GuanJdoJ]

Module not found: Can't resolve 'antd/es/Button'
  1 | import React from 'react'
> 2 | import {Button} from 'antd'

Same error with Nextjs@13.4.8 antd@5.6.4
And temporarily solved by downgrading Nextjs@13.4.7

[RedJue]

Discussions here :#43348

[bennik88]

Same issue.

[nanxiaobei]

Only happens on next@13.4.8, not on next@13.4.7.

[ArvindSteamA]

I think this a compatibility issue with the most recent NextJS release.

If you install version 13.4.7 of next, everything works as expected, but bumping to 13.4.8 surfaces this error.

This worked for me remove ^before 13.4.7 the version if you have.

[bombillazo]

Why was this closed? Is this truly fixed if the solution was to downgrade the package? Is this error an issue with Next or does AntD have to update their packages tp be compatible with the latest Next.js version?

[afc163]

#43348 (comment)

[ycalm]

13.4.9 fix this issue vercel/next.js#52169
another issue vercel/next.js#52307 and can temporarily fix vercel/next.js#52307 (comment)

[bombillazo]

@ycalm

so... its not fixed yet?

[ycalm]

@bombillazo this issue has been fixed, but got another, you can get more detail in vercel/next.js#52307

[furqonat]

now its fixed by using nextjs version 13.4.16