Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

next build doesn't terminate when swcMinify: false and devtool: 'source-map' are set #45276

Closed
1 task done
lforst opened this issue Jan 25, 2023 · 5 comments
Closed
1 task done
Labels
bug Issue was opened via the bug report template.

Comments

@lforst
Copy link
Contributor

lforst commented Jan 25, 2023

Verify canary release

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

Provide environment information

Operating System:
  Platform: linux
  Arch: arm64
  Version: #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022
Binaries:
  Node: 16.19.0
  npm: 8.19.3
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.1.6-canary.1
  eslint-config-next: 13.1.2
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-shmwkm?file=next.config.js

To Reproduce

  1. Create Next.js config with the following:
module.exports = {
  reactStrictMode: true,
  swcMinify: false,
  webpack: (config) => {
    config.devtool = 'source-map';
    return config;
  },
};
  1. Run yarn build
  2. Examine the build being stuck on "Creating an optimized production build ..."

Side note: We noticed this because a lot of users were reporting that their app doesn't build anymore with @sentry/nextjs installed. Some more info with useful reports in this issue: getsentry/sentry-javascript#6782 (comment)

Describe the Bug

The build get stuck and doesn't terminate.

Expected Behavior

Build succeeds.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

@lforst lforst added the bug Issue was opened via the bug report template. label Jan 25, 2023
@Max29a
Copy link

Max29a commented Jan 26, 2023

I am also having this problem and hoping very much for a solution

@Trallp
Copy link

Trallp commented Jan 27, 2023

I think it's related #45005

@0xflumedev
Copy link

Waiting for a fix, major issue

@huozhi
Copy link
Member

huozhi commented Jan 31, 2023

Can you try the latest canary 13.1.7-canary.0? fixed by #45423

@huozhi huozhi closed this as completed Jan 31, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2023

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

5 participants