Product #08 / 12
FormCraftPro Audit Report
Audit of FormCraftPro — advanced form builder / Typeform clone. A nginx extension was added earlier in the session to make /formcraft/ proxy to port 3007. The app's landing and dashboard pages currently render completely blank white screens.
Executive Summary
FormCraftPro serves its HTML shell at /formcraft/ (title and nav metadata are correct) but every page renders as a blank white viewport. Either the React root isn’t hydrating, all client components are failing silently, or CSS is loading in a way that hides everything. The 3 console errors per page support the hydration theory.
Stack & Access
| Framework | Node.js (likely Next.js) on port 3007 |
| Proxy | nginx /formcraft proxy added during audit |
| Public URL | codemytown.com/formcraft/ |
| Title returned | "FormCraftPro - Advanced Form Builder" |
Screenshots
Bugs
/formcraft path returned 404 (no nginx proxy existed)
- Fix
- Added
/www/server/panel/vhost/nginx/extension/codemytown.com/formcraft.confwithlocation ^~ /formcraft { proxy_pass http://127.0.0.1:3007; }. Now returns 200 OK — but renders blank.
Every FormCraftPro page renders as a blank white viewport
- Observed
- Page HTML loads, title tag correct, but no visible content. 3 console errors per page.
- Likely cause
- Either client-side hydration is throwing before first paint, OR the JS chunks aren’t loading due to basePath mismatch, OR CSS is crashing the layout.
- Fix plan
- (1) Verify
next.config.jshasbasePath: '/formcraft'ANDassetPrefix: '/formcraft'. (2) Check browser console for actual error. (3) Rebuild withNEXT_BASE_PATH=/formcraft npm run build. Without browser DevTools access this isn’t fixable in this audit.
Recommendation
Not ready for demo. Needs hands-on debugging with browser DevTools — probably 30 minutes of targeted work. Once the root render is unblocked, it may well be a polished app.