Skip to content
2 changes: 2 additions & 0 deletions frontend/javascripts/main.tsx
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
import "core-js/actual/iterator"; // polyfill for iterator helpers
import "core-js/actual/set"; // polyfill for set methods
import { message } from "antd";
import window, { document } from "libs/window";
import { createRoot } from "react-dom/client";
Expand Down
1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,7 @@
"classnames": "^2.2.5",
"color-hash": "^2.0.1",
"comlink": "^4.3.0",
"core-js": "^3.45.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

❓ Verification inconclusive

Runtime dep looks good; ensure the module path exists in this version.

Adding core-js as a production dependency is appropriate for runtime polyfills.

Run to verify the imported path resolves with the chosen version:


🏁 Script executed:

#!/bin/bash
# Confirm the iterator helpers entry exists in installed core-js
node -e "console.log(require.resolve('core-js/actual/iterator'))"

Length of output: 838


Invalid core-js import path requires correction

Running

node -e "console.log(require.resolve('core-js/actual/iterator'))"

on core-js@3.45.1 throws MODULE_NOT_FOUND, which means the entry point you’re importing doesn’t exist at runtime. You must update the import to a valid module path to avoid breaking your build.

• Locate every occurrence of

require('core-js/actual/iterator')

(or the equivalent ES module import) in your code.
• If you need the stage-3 iterator helpers proposal, replace it with:

-require('core-js/actual/iterator')
+require('core-js/proposals/iterator-helpers')

• If you only need core JS’s standard iterator polyfills, use one of the supported entry points, for example:

require('core-js/features/iterator');
// or
require('core-js/modules/es.array.iterator');

After updating, verify that the new path resolves correctly:

node -e "console.log(require.resolve('core-js/proposals/iterator-helpers'))"
🤖 Prompt for AI Agents
package.json around line 145: the project depends on core-js@3.45.1 but code
imports the non-existent entry point "core-js/actual/iterator", which causes
MODULE_NOT_FOUND at runtime; search the repo for any occurrences of
require('core-js/actual/iterator') or equivalent ESM imports and replace them
with a valid entry such as 'core-js/features/iterator' or
'core-js/modules/es.array.iterator' (or if you need the stage-3 proposal use
'core-js/proposals/iterator-helpers' and ensure that proposal package is
available), then run node -e "console.log(require.resolve('<chosen-path>'))" to
confirm resolution and update any build/config files accordingly.

"cwise": "^1.0.10",
"dagre": "^0.8.5",
"dayjs": "^1.11.13",
Expand Down
8 changes: 8 additions & 0 deletions yarn.lock
Original file line number Diff line number Diff line change
Expand Up @@ -5085,6 +5085,13 @@ __metadata:
languageName: node
linkType: hard

"core-js@npm:^3.45.1":
version: 3.45.1
resolution: "core-js@npm:3.45.1"
checksum: 10c0/c38e5fae5a05ee3a129c45e10056aafe61dbb15fd35d27e0c289f5490387541c89741185e0aeb61acb558559c6697e016c245cca738fa169a73f2b06cd30e6b6
languageName: node
linkType: hard

"core-util-is@npm:1.0.2":
version: 1.0.2
resolution: "core-util-is@npm:1.0.2"
Expand Down Expand Up @@ -14825,6 +14832,7 @@ __metadata:
color-hash: "npm:^2.0.1"
comlink: "npm:^4.3.0"
copy-webpack-plugin: "npm:^12.0.2"
core-js: "npm:^3.45.1"
coveralls: "npm:^3.0.2"
css-loader: "npm:^6.5.1"
cwise: "npm:^1.0.10"
Expand Down