Stockfish 16 NNUE fails to load (dynamic module import error) • page 1/1 • Lichess Feedback • lichess.org

Both versions of SF 16 NNUE are affected. SF 14 works.

Uncaught error { target: Worker, isTrusted: true, message: "Error: Dynamic module import is disabled or not supported in this context", filename: "https://lichess.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.worker.js", lineno: 1, colno: 1149, srcElement: Worker, eventPhase: 0, bubbles: false, cancelable: true, ... }

onerror https://lichess1.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.js:22

Error: Dynamic module import is disabled or not supported in this context linrock-nnue-7.worker.js:1:1149
handleMessage https://lichess.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.worker.js:1

I hope this helps tracking down the bug. Thank you Lichess dev team for your continued work on this site!

Both versions of SF 16 NNUE are affected. SF 14 works. Uncaught error { target: Worker, isTrusted: true, message: "Error: Dynamic module import is disabled or not supported in this context", filename: "https://lichess.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.worker.js", lineno: 1, colno: 1149, srcElement: Worker, eventPhase: 0, bubbles: false, cancelable: true, ... } onerror https://lichess1.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.js:22 Error: Dynamic module import is disabled or not supported in this context linrock-nnue-7.worker.js:1:1149 handleMessage https://lichess.org/assets/_a022fa/npm/lila-stockfish-web/linrock-nnue-7.worker.js:1 I hope this helps tracking down the bug. Thank you Lichess dev team for your continued work on this site!

schlawg

This seems unrelated to our CDN troubles. Mind if I ask what browser and platform you're running?

swearbyforce

@schlawg said in #2:

This seems unrelated to our CDN troubles. Mind if I ask what browser and platform you're running?

Oh, I didn't realize it could be something on my end, my bad! Upgraded the browser (Firefox 102.10 ESR -> 115.4 ESR) and the issue is now fixed. Debian Linux 11. This is shared setup on a lab PC nobody really maintains so that explains the ancient browser, I wasn't sure if I could update it but glad I could.

@schlawg said in #2: > This seems unrelated to our CDN troubles. Mind if I ask what browser and platform you're running? Oh, I didn't realize it could be something on my end, my bad! Upgraded the browser (Firefox 102.10 ESR -> 115.4 ESR) and the issue is now fixed. Debian Linux 11. This is shared setup on a lab PC nobody really maintains so that explains the ancient browser, I wasn't sure if I could update it but glad I could.