next.js: Module not found: Can't resolve '@builder.io/partytown/integration'

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 19.6.0: Tue Feb 15 21:39:11 PST 2022; root:xnu-6153.141.59~1/RELEASE_X86_64
    Binaries:
      Node: 14.18.1
      npm: 8.1.0
      Yarn: 1.22.10
      pnpm: 6.32.2
    Relevant packages:
      next: 12.1.2-canary.0
      react: 17.0.2
      react-dom: 17.0.2

What browser are you using? (if relevant)

Not relevant

How are you deploying your application? (if relevant)

Vercel, next build

Describe the Bug

warn  - Compiled with warnings

./node_modules/next/dist/pages/_document.js
Module not found: Can't resolve '@builder.io/partytown/integration' in '…'

Import trace for requested module:
./node_modules/next/document.js
./src/pages/_app.tsx

To ignore the warnings, use a custom webpack config:

      config.ignoreWarnings = [
        {
          module: /\.\/node_modules\/next\/dist\/pages\/_document\.js/, 
        },
      ];

Expected Behavior

No warnings. It worked in the last next version 12.1.0.

See recent merge of https://github.com/vercel/next.js/pull/34244

I like that PR. I would love to see a fix, rather than a rollback.

@housseindjirdeh and @ijjk

To Reproduce

Use a custom _app and _document and try building with webpack.

Probably not relevant, but I am using a monorepo and custom webpack config.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 23 (16 by maintainers)

Commits related to this issue

Most upvoted comments

Can you confirm you are no longer having the issue in the latest canary? It should be fully resolved now.

Yup! I just tested, and I no longer have the issue while using canary 🥳

Thank you @ijjk 👍 I really appreciate your help and patience