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
With next@11, the above import can simply be replaced with import { NextConfig } from 'next'. AFAIK that would only be compatible with Next@11, so the peer dependency would have to be narrowed to ^11.0.0.
The text was updated successfully, but these errors were encountered:
Using
[email protected]
,[email protected]
and[email protected]
, the following happens during build:This is caused by these changes to Next.js: vercel/next.js#26756
With
next@11
, the above import can simply be replaced withimport { NextConfig } from 'next'
. AFAIK that would only be compatible with Next@11, so the peer dependency would have to be narrowed to^11.0.0
.The text was updated successfully, but these errors were encountered: