Open manumonti opened 3 weeks ago
After some investigation, I couldn't find the cause of this.
Also, I realized this issue was present before the inclusion of TACo to the original OrbisDB demo. For instance, it happens in this commit: 88c0f850562263755ddf1bade05a3d0a8a60bce3
@rainbow-me/rainbowkit
, @wagmi/core
and wagmi
to latest versions.SyntaxError: "" literal not terminated before end of script lockdown-install.js:1:97687
functors moz-extension://11ed251a-a097-4f98-89fe-befeebbd068e/scripts/lockdown-install.js:1
(Async: EventListener.handleEvent)
functors moz-extension://11ed251a-a097-4f98-89fe-befeebbd068e/scripts/lockdown-install.js:1
functors moz-extension://11ed251a-a097-4f98-89fe-befeebbd068e/scripts/lockdown-install.js:1
lockdown moz-extension://11ed251a-a097-4f98-89fe-befeebbd068e/scripts/lockdown-install.js:1
<anonymous> moz-extension://11ed251a-a097-4f98-89fe-befeebbd068e/scripts/lockdown-run.js:4
And after some time:
ChunkLoadError: Loading chunk app/layout failed.
(timeout: http://localhost:3000/_next/static/chunks/app/layout.js)
NextJS 4
loadChunk react-server-dom-webpack-client.browser.development.js:244
preloadModule react-server-dom-webpack-client.browser.development.js:170
resolveModule react-server-dom-webpack-client.browser.development.js:1813
processFullRow react-server-dom-webpack-client.browser.development.js:1902
processBinaryChunk react-server-dom-webpack-client.browser.development.js:2072
progress react-server-dom-webpack-client.browser.development.js:2153
promise callback*progress react-server-dom-webpack-client.browser.development.js:2154
promise callback*progress react-server-dom-webpack-client.browser.development.js:2154
promise callback*startReadingFromStream react-server-dom-webpack-client.browser.development.js:2161
createFromReadableStream react-server-dom-webpack-client.browser.development.js:2166
<anonymous> app-index.tsx:121
NextJS 4
<anonymous> app-next-dev.ts:7
appBootstrap app-bootstrap.ts:61
loadScriptsInSequence app-bootstrap.ts:20
appBootstrap app-bootstrap.ts:60
<anonymous> app-next-dev.ts:6
NextJS 7
lockdown-install.js:1:97687
functors lockdown-install.js:1
invokeGuardedCallbackImpl react-dom.development.js:20614
invokeGuardedCallback react-dom.development.js:20689
beginWork react-dom.development.js:26949
performUnitOfWork react-dom.development.js:25748
workLoopConcurrent react-dom.development.js:25734
renderRootConcurrent react-dom.development.js:25690
performConcurrentWorkOnRoot react-dom.development.js:24504
workLoop scheduler.development.js:256
flushWork scheduler.development.js:225
performWorkUntilDeadline scheduler.development.js:534
(Async: EventHandlerNonNull)
<anonymous> scheduler.development.js:569
<anonymous> scheduler.development.js:630
NextJS 4
<anonymous> index.js:6
NextJS 4
<anonymous> react-dom.development.js:27
<anonymous> react-dom.development.js:38595
NextJS 4
<anonymous> index.js:37
NextJS 4
<anonymous> client.js:3
NextJS 4
<anonymous> app-index.js:15
NextJS 4
<anonymous> app-next-dev.ts:7
appBootstrap app-bootstrap.ts:61
loadScriptsInSequence app-bootstrap.ts:20
appBootstrap app-bootstrap.ts:60
<anonymous> app-next-dev.ts:6
NextJS 7
Hi @manumonti - are you encountering the same issue with the latest version?
Unfortunately, yes.
And after this, waiting a time, it crashes.
If you run for first time the webapp through
pnpm dev
, anything is loaded and, after a while, it crashes with a timeout error. If you refresh, then the web app loads sucessfully.