The error doesn't show a specific file location. Let me search systematically for where script tags might be rendered in React components:

Found it! The files with script tags are app/layout.tsx and components/ui/chart.tsx. Let me examine both:

I found the issue. The chart.tsx component is using a <style> tag with dangerouslySetInnerHTML, which is correct. However, the layout.tsx file is using a <Script> component with dangerouslySetInnerHTML and has incomplete HTML content (the __html is cut off at line 100).

Let me read the full layout.tsx to see the complete script:

I found the issue. The problem is that you have Suspense components wrapping client components that use server-side APIs or cause hydration mismatches. The error about script tags is likely coming from the Suspense fallback trying to render during the client-side hydration phase. The core issue is wrapping components in Suspense in the body when they're client components.

Let me remove the problematic Suspense wrappers from the body and keep only the ones in the head (which are correctly used):

Now I also need to remove the unused Suspense import since we're no longer using it in the body:

Fixed the script tag error by removing unnecessary Suspense wrappers from client components in the layout body. Suspense is for server components and async operations—client components like Navbar, WhatsAppButton, and EnhancedPhoneTracker should render directly without Suspense boundaries. This eliminates the hydration mismatch that was causing React to encounter script tags during rendering.

I see the issue. The contact page uses useSearchParams(), which requires a Suspense boundary. I previously deleted the loading.tsx file, but it's needed for Next.js 15+ to handle the Suspense requirement. Let me check the contact page and create the proper loading component:

The contact page is a client component that uses useSearchParams() on line 21. In Next.js 15+, this requires a Suspense boundary with a loading fallback. The solution is to create a loading.tsx file that Next.js will use as the Suspense fallback. Let me create it:

I've created the app/contact/loading.tsx file with a loading component that serves as the Suspense boundary fallback for the contact page. Next.js 15+ automatically wraps dynamic pages in Suspense, and the loading.tsx file provides the fallback UI that displays while useSearchParams() is being resolved on the client. This resolves the deployment error while maintaining a smooth user experience with a spinner and loading message.