You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Next.js 11.1.3-canary.69, ESM externals has been turned on by default using the experimental: { esmExternals: true } in this commit.
Unfortunately ESM external is still not compatible with a lot of packages and the only way to turn it off is by setting the following config:
experimental: { esmExternals: false }
The problem is that any configuration set under experimental triggers the following warning logs, which for this case seems misleading:
warn - You have enabled experimental feature(s).
warn - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.
nbouvrette
changed the title
Disabling esmExternals generated a misleading warning message
Disabling esmExternals generates a misleading warning message
Jan 25, 2022
Run
next info
(available from version 12.0.8 and up)What version of Next.js are you using?
v12.0.8
What version of Node.js are you using?
16.6
What browser are you using?
Chrome
What operating system are you using?
Windows
How are you deploying your application?
Vercel
Describe the Bug
Since Next.js
11.1.3-canary.69
, ESM externals has been turned on by default using theexperimental: { esmExternals: true }
in this commit.Unfortunately ESM external is still not compatible with a lot of packages and the only way to turn it off is by setting the following config:
experimental: { esmExternals: false }
The problem is that any configuration set under
experimental
triggers the following warning logs, which for this case seems misleading:This is related to #33148
Expected Behavior
I would expect that
esmExternals
is moved fromexperimental
to "top-level" and stops triggering the warning.To Reproduce
Simply set
experimental: { esmExternals: false }
innext.config.js
The text was updated successfully, but these errors were encountered: