Issue: Custom component CropUpload not appearing in Plasmic Studio component list despite successful app host setup.
What’s Working:
-
App host URL loads correctly: https://ezmarketing-space.vercel.app/plasmic-host
-
Vercel deployment succeeds without errors
-
“Your app is ready to host Plasmic Studio!” message displays properly
What’s Not Working:
-
CropUpload component doesn’t appear in Plasmic Studio’s component insertion menu
-
Debug console logs from plasmic-init.ts are not visible anywhere (browser console or Vercel logs)
Key Technical Details:
-
Component registered in
plasmic-init.ts(not plasmic-host.tsx)
-
Registration includes required
props: {}property -
Uses
isDefaultExport: trueand correct import path -
Added extensive debug logging with emoji markers - none appear in console
Critical Observation:
The debug logs with emoji markers (
, ) are completely absent from both browser console and deployment logs. This suggests plasmic-init.ts may not be executing at all, despite successful deployment.
Similar Cases:
This matches patterns where component registration code appears correct but the registration file isn’t being executed properly in the app host context.
Request:
Please investigate why plasmic-init.ts execution isn’t producing expected console output in the app host environment, preventing component registration from completing.
I tried my best to explain my problem clearly and with as much detail as possible. I hope Jason will read it carefully before declaring that I wasn’t clear and deleting my problem.