Closed Pipe-Runner closed 3 years ago
Hm, I wonder if anyone has succeeded with nextjs 12.
This is just off the top of my head, but I remember them shipping an odd bug with the latest v12 minor update, which is temporarily fixed by adding experimental: { esmExternals: false, },
to your nextConfig
object. They acknowledged the issue so i expect it to be solved soon (or already, haven't checked yet). Hopefully this helps you!
@AakashMallik You solve this issue?
This is just off the top of my head, but I remember them shipping an odd bug with the latest v12 minor update, which is temporarily fixed by adding
experimental: { esmExternals: false, },
to yournextConfig
object. They acknowledged the issue so i expect it to be solved soon (or already, haven't checked yet). Hopefully this helps you!
This fixed the build. Thanks.
Pardon me for my ignorance if I have missed something obvious: Note: This worked just fine before Next12
Today I bumped up NextJS from 11 to 12 and since then, this is what I get while building my app.
My configurations are as follows:
package.json
tsconfig.json
next.config.js