Bug Report: ChunkLoadError when loading lazy-loaded frontend bundle

[DataStrategistTeam]

Bug description

Superset displays an "Unexpected error" page with the following error:

ChunkLoadError: Loading chunk 4169 failed.

The application fails while attempting to load a lazily loaded frontend bundle, resulting in a broken UI and preventing access to the affected page.

Unexpected error
ChunkLoadError: Loading chunk 4169 failed.

Lazy
l@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1116:190
98837/g/<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7054
main
2672/h1<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:340:4725
98837/g/<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7054
div
2672/h2<@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:340:4989
Suspense
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:20127
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:20770
tD@http://127.0.0.1:8088/static/assets/spa.72ab05fb3acc832bdf24.entry.js:301:8750
R@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:7:873
n@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:93148
x@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:7:1072
e3@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1501:3086
c@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1412:2136
79551/s<@http://127.0.0.1:8088/static/assets/2290.4aef28ca85361c2fdbd3.entry.js:273:13694
C@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:554:29987
rd@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:8092
rv@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:9872
rb@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:103:13885
y@http://127.0.0.1:8088/static/assets/vendors.6f4ecbc3d2e23e236060.entry.js:58:7234
SupersetThemeProvider@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1:3726
i@http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js:1541:18426
tH@http://127.0.0.1:8088/static/assets/spa.72ab05fb3acc832bdf24.entry.js:301:9615
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:17228
t@http://127.0.0.1:8088/static/assets/8706.6dfab372988d20453152.entry.js:6:8222
tW
See less

I verified that Superset is serving static assets correctly.

For example, opening the following asset directly in the browser returns the JavaScript file successfully:

http://127.0.0.1:8088/static/assets/8115.ef2c25320df8c6b15d8a.entry.js

The file is accessible and downloads/loads without error.

Despite this, the application still throws:

ChunkLoadError: Loading chunk 4169 failed.

Screenshots/recordings

No response

Superset version

master / 6.1

Python version

3.11

Node version

20

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

This is a known issue that has been reported before (see #39219). ChunkLoadError is almost always caused by stale cached assets — the browser holds a reference to a JS/CSS chunk from a previous build after a deploy or version change [1].

A hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or clearing the browser cache typically resolves this.

However, there are two things worth noting for your environment:

1. Node version mismatch: You're using Node 16, but the current master branch requires Node ^20.16.0 (recommended v20.18.3 per the .nvmrc file) [2] [3]. Building the frontend assets with an unsupported Node version can produce broken or incompatible chunks. This is very likely the root cause of your issue.

2. No built-in retry logic: Superset does not currently implement any retry mechanism for failed chunk loads — it relies on standard React ErrorBoundary and Suspense patterns [4].

Recommended fix: Upgrade to Node 20 (specifically v20.18.3), rebuild your frontend assets (npm ci && npm run build), clear your browser cache, and try again.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[rusackas]

I think the bot is right that this might just not be something we can fix... but if you can pinpoint a Superset bug rather than a config/version problem in your implementation, we can try to address it. Let us know.