chore(supabase): full purge — remove all Supabase references from codebase
- Delete supabase/ directory (config.toml, push-migrations.js, ADMIN_CREATE_STOP_FIX.sql, 137 archived migration files) - Remove @supabase/ssr and @supabase/supabase-js from package.json - Strip *.supabase.co from next.config.ts image hostnames - Strip https://*.supabase.co from vercel.json CSP connect-src - Remove 'supabase/**' ignore from eslint.config.mjs - Clean supabase references from src/lib/db.ts, vitest.config.ts, db/seeds/2026-tuxedo-tour-stops.sql, src/actions/storefront.ts, scripts/import-tuxedo-stops.ts comments - Rewrite env-var docs in README, ENVIRONMENT, PRODUCTION_SETUP, PRODUCTION_DEPLOYMENT_CHECKLIST, LAUNCH_CHECKLIST, CLAUDE, MEMORY, REPORT to drop NEXT_PUBLIC_SUPABASE_URL / SUPABASE_SERVICE_ROLE_KEY / supabase link / supabase CLI references The canonical migration runner is now scripts/migrate.js (uses pg directly via DATABASE_URL). Migrations live in db/migrations/. The Supabase CLI is no longer in the codebase. The only remaining '@supabase/*' in the dep tree is @supabase/auth-js as a transitive of @neondatabase/auth (Neon Auth / Better Auth). Final source scan: grep -rln '@supabase\|rest/v1\|supabase\.co' src/ tests/ db/ scripts/ next.config.ts vercel.json eslint.config.mjs package.json returns zero. Verification: npm install clean (11 added, 21 removed, 12 changed), tsc shows same 17 pre-existing errors (Stripe dahlia API version + fetch preconnect mocks), vitest 172/175 (3 pre-existing failures in getAdminUser.test.ts), lint shows same 14 pre-existing errors. Live-tested: dev server boots in 248ms, public storefronts (/) (/login) (/pricing) (/tuxedo) (/indian-river-direct) all return 200; /admin/v2?demo=1 reaches 200 after dev_session redirect; storefront renders real brand content.
This commit is contained in:
@@ -1,56 +0,0 @@
|
||||
-- Migration 023: Fix cart availability check
|
||||
-- Replaces unreliable client-side product_stops query with a
|
||||
-- SECURITY DEFINER RPC that bypasses RLS and returns structured availability.
|
||||
--
|
||||
-- The cart page's availability check was:
|
||||
-- 1. Unreliable — anon/frontend query may be blocked by RLS or return empty
|
||||
-- 2. Conflating "no rows" with "product is unavailable"
|
||||
-- 3. Blocking all stops even when the query itself failed
|
||||
--
|
||||
-- This adds: check_stop_product_availability(p_stop_id, p_product_ids)
|
||||
-- Returns: { product_id, is_available }[] for each requested product.
|
||||
-- The cart page uses this to show truly incompatible items separately
|
||||
-- from query errors.
|
||||
|
||||
-- ═══════════════════════════════════════════════════════════════════════════
|
||||
-- 1. check_stop_product_availability RPC
|
||||
-- ═══════════════════════════════════════════════════════════════════════════
|
||||
|
||||
CREATE OR REPLACE FUNCTION public.check_stop_product_availability(
|
||||
p_stop_id UUID,
|
||||
p_product_ids UUID[]
|
||||
)
|
||||
RETURNS JSONB
|
||||
LANGUAGE plpgsql SECURITY DEFINER SET search_path = public
|
||||
AS $$
|
||||
DECLARE
|
||||
v_result JSONB := '[]'::JSONB;
|
||||
v_pid UUID;
|
||||
BEGIN
|
||||
FOR v_pid IN SELECT unnest(p_product_ids)
|
||||
LOOP
|
||||
v_result := v_result || jsonb_build_array(jsonb_build_object(
|
||||
'product_id', v_pid,
|
||||
'is_available', EXISTS(
|
||||
SELECT 1 FROM product_stops
|
||||
WHERE stop_id = p_stop_id AND product_id = v_pid
|
||||
)
|
||||
));
|
||||
END LOOP;
|
||||
|
||||
RETURN v_result;
|
||||
END;
|
||||
$$;
|
||||
|
||||
-- ═══════════════════════════════════════════════════════════════════════════
|
||||
-- 2. Update cart/page.tsx to use the RPC + show query errors distinctly
|
||||
-- (done in the application code, not the migration)
|
||||
-- ═══════════════════════════════════════════════════════════════════════════
|
||||
--
|
||||
-- Changes to src/app/cart/page.tsx:
|
||||
-- - handleStopSelect: POST to check_stop_product_availability RPC instead of
|
||||
-- direct product_stops query. Handle errors distinctly from unavailability.
|
||||
-- - Add availabilityError state — if RPC fails, show "Unable to verify
|
||||
-- availability" but allow checkout to proceed (server will catch true errors).
|
||||
-- - Add per-product availabilityError flag to distinguish query failure
|
||||
-- from confirmed unavailability.
|
||||
Reference in New Issue
Block a user