Getting a runtime error caused by Plasmic

Issues
1

Project ID: “xwCKThtqzMdeR2bpew1twn”

Getting:

# Unhandled Runtime Error

Error: PLASMIC: Failed to load render__HkDWFiJpV7S3.js: Error: Unknown module chunk-Z3Q2F5UW.js

## Call Stack

### Registry.load

node_modules/@plasmicapp/loader-core/dist/index.esm.js (223:0)

### ComponentLookup.getComponent

node_modules/@plasmicapp/loader-react/dist/index.esm.js (683:0)

### usePlasmicComponent

node_modules/@plasmicapp/loader-react/dist/index.esm.js (1260:0)

### PlasmicComponent

node_modules/@plasmicapp/loader-react/dist/index.esm.js (1305:0)

### renderWithHooks

node_modules/react-dom/cjs/react-dom.development.js (16305:0)

### mountIndeterminateComponent

node_modules/react-dom/cjs/react-dom.development.js (20074:0)

### beginWork

node_modules/react-dom/cjs/react-dom.development.js (21587:0)

### HTMLUnknownElement.callCallback

node_modules/react-dom/cjs/react-dom.development.js (4164:0)

### Object.invokeGuardedCallbackDev

node_modules/react-dom/cjs/react-dom.development.js (4213:0)

### invokeGuardedCallback

node_modules/react-dom/cjs/react-dom.development.js (4277:0)

### beginWork$1

node_modules/react-dom/cjs/react-dom.development.js (27451:0)

### performUnitOfWork

node_modules/react-dom/cjs/react-dom.development.js (26557:0)

### workLoopSync

node_modules/react-dom/cjs/react-dom.development.js (26466:0)

### renderRootSync

node_modules/react-dom/cjs/react-dom.development.js (26434:0)

### performConcurrentWorkOnRoot

node_modules/react-dom/cjs/react-dom.development.js (25738:0)

### workLoop

node_modules/scheduler/cjs/scheduler.development.js (266:0)

### flushWork

node_modules/scheduler/cjs/scheduler.development.js (239:0)

### MessagePort.performWorkUntilDeadline

node_modules/scheduler/cjs/scheduler.development.js (533:0)

I have published a new version to the staging tag on Plasmic (project version 22.0.0).

I’m running “@plasmicapp/loader-nextjs”: “^1.0.377” as of today

plasmic-init.js

  • version: ‘staging’
  • preview: false,
2

setting preview: true makes the issue go away, despite no new changes since “staging” was published.

3

@sarah_ahmed can you look into this? sorry to ping but I’ve been unable to push to production for several days because of this issue.

4

Can you also share the repository link and the command that throws the error? Thank you

5

The repo is private. Can I invite you on github?

6

Sure please do

7

While we investigate the issue, can you change your PLASMIC.maybeFetchComponentData and PLASMIC.fetchComponentData calls to be like ([firstParamenter], { deferChunks: false }) and see if it works?

8

Hi

I’ve just changed it for the Dashboard page and it seems to make the error go away. Shall I proceed with this fix for production?

9

Yes, you can use this in production without an issue.

1 Like
10

Thanks for the solution @icaro_guerra, it solved the same issue for me. Could you explain what setting deferChunks: false does?

11

deferChunks is a feature we have to decrease initial bundle size by splitting it in chunks. While we fix bugs of the new feature, you can use deferChunks: false to unblock.