If you start using the latest version of next.js, which is 13, you might have the issue below.

The simple fix is adding the option below
{
...
"verbatimModuleSyntax": true,
...
}
Click to see the source from the Github pull request discussion.
If you start using the latest version of next.js, which is 13, you might have the issue below.
The simple fix is adding the option below
{
...
"verbatimModuleSyntax": true,
...
}
Click to see the source from the Github pull request discussion.