-
-
Notifications
You must be signed in to change notification settings - Fork 34.1k
Open
Description
Version
24.12.0
Platform
Linux anto-DELL 6.14.0-37-generic #37~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 20 10:25:38 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
react-konva
What steps will reproduce the bug?
Just do npm run build. After some of the usual build output you get this error:
> node src/utils/next/deleteBuildDir.js && next build
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
▲ Next.js 16.0.3 (Turbopack)
- Environments: .env.production, .env
- Experiments (use with caution):
✓ scrollRestoration
✓ Finished TypeScript in 8.4s
Creating an optimized production build ...
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
✓ Compiled successfully in 16.1s
Collecting page data using 7 workers ...[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
Collecting page data using 7 workers .[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
Collecting page data using 7 workers ..Error: Failed to load external module react-konva: Error [ERR_INTERNAL_ASSERTION]: Unexpected module status 0. Cannot require() ES Module /home/anto/Development/Luminous/lumi_app/node_modules/konva/lib/index.js because it is not yet fully loaded.
This may be caused by a race condition if the module is simultaneously dynamically import()-ed via Promise.all().
Try await-ing the import() sequentially in a loop instead.
(From /home/anto/Development/Luminous/lumi_app/node_modules/react-konva/lib/ReactKonva.js in non-loader-hook thread)
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:514:15)
at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__9a4294e0._.js:1:8315)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:715:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:738:12)
at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:228:20)
at <unknown> (.next/server/chunks/ssr/_0b288f18._.js:1:1373)
at Context.asyncModule [as a] (.next/server/chunks/ssr/[turbopack]_runtime.js:434:5)
at module evaluation (.next/server/chunks/ssr/_0b288f18._.js:1:1295)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:715:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:738:12)
> Build error occurred
Error: Failed to collect page data for /innovation-space/[projectId]/[workflowId]
at ignore-listed frames {
type: 'Error'
}
How often does it reproduce? Is there a required condition?
It is systematic.
With Node version 24.11.1 the build works as expected.
What is the expected behavior? Why is that the expected behavior?
The build should succeed.
This the expected output of npm run build with Node version 24.11.1:
> node src/utils/next/deleteBuildDir.js && next build
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
▲ Next.js 16.0.3 (Turbopack)
- Environments: .env.production, .env
- Experiments (use with caution):
✓ scrollRestoration
✓ Finished TypeScript in 8.1s
Creating an optimized production build ...
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
✓ Compiled successfully in 12.2s
Collecting page data using 7 workers ..[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
✓ Collecting page data using 7 workers in 2.5s
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
✓ Generating static pages using 7 workers (13/13) in 1373.2ms
✓ Finalizing page optimization in 6.1ms
Route (pages)
┌ /_app
├ ○ /404 (941 ms)
├ ○ /ai-customers
├ ƒ /api/auth/keycloak/callback
├ ƒ /api/auth/logout
├ ○ /experts (942 ms)
├ ○ /experts/[id] (943 ms)
├ ○ /experts/all (942 ms)
├ ○ /experts/recently-active (940 ms)
├ ○ /innovation-space (941 ms)
├ ○ /innovation-space-group/[id] (940 ms)
├ ○ /innovation-space/[projectId]
├ ○ /innovation-space/[projectId]/[workflowId]
├ ○ /shared-card/[uid]
├ ƒ /space-converter
└ ○ /tutorial (941 ms)
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
What do you see instead?
> node src/utils/next/deleteBuildDir.js && next build
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
▲ Next.js 16.0.3 (Turbopack)
- Environments: .env.production, .env
- Experiments (use with caution):
✓ scrollRestoration
✓ Finished TypeScript in 8.4s
Creating an optimized production build ...
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
✓ Compiled successfully in 16.1s
Collecting page data using 7 workers ...[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
Collecting page data using 7 workers .[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
Collecting page data using 7 workers ..Error: Failed to load external module react-konva: Error [ERR_INTERNAL_ASSERTION]: Unexpected module status 0. Cannot require() ES Module /home/anto/Development/Luminous/lumi_app/node_modules/konva/lib/index.js because it is not yet fully loaded.
This may be caused by a race condition if the module is simultaneously dynamically import()-ed via Promise.all().
Try await-ing the import() sequentially in a loop instead.
(From /home/anto/Development/Luminous/lumi_app/node_modules/react-konva/lib/ReactKonva.js in non-loader-hook thread)
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:514:15)
at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__9a4294e0._.js:1:8315)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:715:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:738:12)
at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:228:20)
at <unknown> (.next/server/chunks/ssr/_0b288f18._.js:1:1373)
at Context.asyncModule [as a] (.next/server/chunks/ssr/[turbopack]_runtime.js:434:5)
at module evaluation (.next/server/chunks/ssr/_0b288f18._.js:1:1295)
at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:715:9)
at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:738:12)
> Build error occurred
Error: Failed to collect page data for /innovation-space/[projectId]/[workflowId]
at ignore-listed frames {
type: 'Error'
}
Additional information
The problem is not limited to Ubuntu Linux 24.04. It occurs in exactly the same way on MacOS 26.0.1 and on Arch Linux, with kernel v6.17.9.arch1-1
Metadata
Metadata
Assignees
Labels
No labels