The package.json looks fine. The error mentions npm:stripe@17.7.0 specifically but the package.json has ^20.1.0. This suggests there might be a lockfile or cache issue. Let me also check if there's a @supabase/ssr package missing that's being imported somewhere:

The package.json is missing @supabase/ssr which is needed for the Supabase client. Let me add it along with ensuring proper version formats:

Added @supabase/ssr package (v0.6.1), updated @supabase/supabase-js to v2.49.4, and pinned stripe to v17.7.0 (the version the build was looking for). These changes should resolve the package resolution errors during deployment.

The package.json looks correct. The issue is that bun is having trouble resolving these packages. This is likely a Vercel/bun caching issue. Let me check if there's a bun.lock or bun.lockb file that might be causing conflicts, and also check if there are any issues with the package versions:

Removed the ^ prefix from @supabase/ssr, @supabase/supabase-js, and stripe to pin them to exact versions, and added "packageManager": "npm@10.8.0" to force npm instead of bun for installation. This should resolve the package resolution errors during deployment.