Error: unknown field lazy
, expected resolveFully
#93
Closed
DuCanhGH
announced in
Announcements
Replies: 1 comment 2 replies
-
@DuCanhGH in this PR, all changes for es6 configuration removed the extra options, the awkward situation is for nodenext configuration, I shared a comment here trying to help |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If you see the error above when you use
next-pwa
with a custom worker,PluginOptions.fallbacks
, orPluginOptions.cacheOnFrontEndNav
, please run the following:This issue seems to have been happening since
@swc/[email protected]
, so yeah. Removingmodule.lazy
andmodule.importInterop
from ourswcConfig
works, but they don't seem to have been removed, so this is most likely a bug.Beta Was this translation helpful? Give feedback.
All reactions