fee0a0687d7bd812.js:510 GET https://v0-feature-rank-dashboard.vercel.app/fonts/Geist_Bold.json 404 (Not Found)
fc @ fee0a0687d7bd812.js:510
fh @ fee0a0687d7bd812.js:510
cN @ fee0a0687d7bd812.js:386
fd @ fee0a0687d7bd812.js:510
(anonymous) @ fee0a0687d7bd812.js:510
e0 @ fee0a0687d7bd812.js:393
nn @ fee0a0687d7bd812.js:393
nE @ fee0a0687d7bd812.js:393
iI @ fee0a0687d7bd812.js:393
(anonymous) @ fee0a0687d7bd812.js:393
i_ @ fee0a0687d7bd812.js:393
ec @ fee0a0687d7bd812.js:393
P @ fee0a0687d7bd812.js:1
2VM315:1 Uncaught SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
fee0a0687d7bd812.js:1 THREE.WebGLRenderer: Context Lost., Application error: a client-side exception has occurred while loading v0-feature-rank-dashboard.vercel.app (see the browser console for more information).
The hero scene doesn't use Text3D. Let me search for what's using the Geist_Bold.json font:
The error mentions Geist_Bold.json which is a 3D font file. The issue might be coming from a cached or previous version of the app trying to load the font. Let me check the CEO mode view since it has 3D-like features:
The hero scene only imports Float from drei. The font error is likely from a browser cache or previous deployment. The main issue is the WebGL context loss. Let me completely disable 3D and use only the CSS gradient fallback to prevent any WebGL issues:
I've completely replaced the WebGL-based 3D scene with a pure CSS animated background. The new implementation uses CSS gradients, blur effects, and keyframe animations to create floating shapes and glowing elements without any WebGL dependency. This eliminates all Three.js/WebGL context loss errors and font loading issues while still providing an engaging visual experience on the landing page.
The Share functionality is already implemented in the header. The issue is that btoa doesn't handle Unicode characters well. Let me fix the encoding to properly handle all characters and also add a toast notification when loading shared state:
Now let me update the features context to properly decode the shared state and show a toast when loading:
Now let me update the header to show a notification when data was loaded from a shared link:
I've improved the Share functionality with the following enhancements:
encodeURIComponent/decodeURIComponent combined with btoa/atob to handle special characters in feature names.document.execCommand("copy") for browsers that don't support the modern Clipboard API.state parameter to prevent confusion and allow fresh sharing.