hey there!
We’ve got a fairly sizable site running on Plasmic + Nextjs which lives on an AWS ec2 instance. Today, for unknown reasons, something on our plasmic site started triggering a “Client side exception” which is killing our Next app.
See an example url here: Member Resources | Foodsmart Nutrition Network (may or may not happen on pageload-- try reloading or clicking around the site if you don’t see the triggered error)
related console error text appears as follows:
TypeError: Cannot read properties of null (reading 'id')
at eval (eval at load (850-69091512cda87041.js:1:4435), <anonymous>:4:21078)
at rC (850-69091512cda87041.js:24:20831)
at rb (6da99a5e-29ce1a8c955a65a5.js:1:40329)
at iU (6da99a5e-29ce1a8c955a65a5.js:1:116116)
at o2 (6da99a5e-29ce1a8c955a65a5.js:1:94369)
at 6da99a5e-29ce1a8c955a65a5.js:1:94191
at o1 (6da99a5e-29ce1a8c955a65a5.js:1:94198)
at oV (6da99a5e-29ce1a8c955a65a5.js:1:91685)
at oB (6da99a5e-29ce1a8c955a65a5.js:1:91110)
at MessagePort.w (424-252a8a380d026401.js:1:99167)
I’m guessing it’s related to an error being thrown by some unknown code in our plasmic components, but we have a LOT of components and pages which would take far too long to comb through manually-- especially as I’ve already thrown a few hours at that.
I have tried reverting to our last known good state from last week, but the Client Side site-killing exception remains.
I’ve had a great many similar issues in the past, stemming from Plasmic not giving any hint or indication at where the js code in question might live. Is there anyway I can gain insight into what’s actually breaking? Thank you!
