hmm… I might be looking at the wrong thing, but my server is currently saying 7.24.2 … need to check if I am looing at the right thing…
are there any recent changes on your side that would break on node 7.x?
NEVER MIND
server is running 16.18.0
@chungwu ^
hmm still can’t repro with node 16 
I am running these versions:
"@plasmicapp/loader-react": "1.0.172",
"@plasmicapp/react-web": "^0.2.106",
"@plasmicpkgs/plasmic-basic-components": "^0.0.85",
would be happy to upgrade on our staging server to see if that fixes it… What are you on?
you could try upgrading loader-react to latest (1.0.184)
Ok, I’ll do that and correct the skipFonts argument,… Will take a couple hours to update and deploy
I’ll keep digging on my end
thank you 
@chungwu still failing…
I’ll keep digging here… Assuming you have not found anything?
It happens to any page… Not just the one pointed to above…
@chungwu I am seeing this message… not sure if it is new or not:
Calling PlasmicComponentLoader.registerModules() after Plasmic component has rendered; starting over.
… though based on code looks like it is just re-registering components…
yeah don’t think that’s related…
@chungwu in my testsuite I have copied some older plasmic pages (copied the JSON), and these render fine …
This makes me believe something happened to the output from plasmic… and/or something changed so the interpreting code fails…
I have a database snapshot I am workin on from a week ago, that has JSON for all the pages that were live at that time, and they all render fine when I test them locally…