'remix' 검색 결과

Checks React Router v7 action conventions: validation errors returned as data with 4xx status (not thrown), redirect on success, and 3-branch ErrorBoundary handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects route data fetched in useEffect instead of loaders, server/client API leaks across loader boundaries, and missing HydrateFallback in React Router v7 framework mode.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Type-safe URL query state management with nuqs 2.x. Use when writing or reviewing code that uses useQueryState, useQueryStates, URL search params, query parameters, nuqs parsers, createLoader, createSearchParamsCache, createSerializer, or URL state in Next.js, React, Remix, React Router, or TanStack Router.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy and configure web frameworks on Netlify — build settings and SSR/edge adapters plus local platform emulation and env vars. Use when setting up or fixing a framework deploy (Next.js / Astro / Nuxt / SvelteKit / Remix / React Router / TanStack Start / SolidStart / Gatsby / Angular / Vite / Express / Hydrogen / Hugo / Eleventy / Vue / React), adding SSR or edge functions or middleware wired to Netlify context, fixing SPA redirect and catch-all rules, setting a build command or publish directory, or debugging "why isn't my env var updating" and framework build failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. Use when: shopify app, shopify, embedded app, polaris, app bridge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate or edit images using the OpenAI Image API (gpt-image-2). Use when the user asks to generate, create, draw, render, illustrate, mock up, or edit an image, icon, logo, mockup, illustration, OG image, blog hero, marketing asset, or similar visual. Also use when the user supplies a reference image and asks to modify, restyle, or remix it. Triggers on: "generate an image", "create an image", "make a picture of", "edit this image", "restyle this", "make a mockup of", "draw a", "render a", "illustration of".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React Router v8 (RR8、旧 Remix) の Framework / Data / Declarative Mode リファレンス。 loader, action, middleware, routes.ts, shouldRevalidate、createBrowserRouter, RouterProvider, BrowserRouter、 hooks (useLoaderData, useActionData, useFetcher, useNavigate, useNavigation, useParams, useSearchParams)、 Form, Link, NavLink, Outlet, Route, Routes, Await、SSR / SPA / Static / RSC、ErrorBoundary, redirect, defer (v7 で削除), session, matchPath, matchRoutes, type-safe routing。 TanStack Router (@tanstack/react-router) とは別ライブラリ。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nuqs (Type-safe URL search params 状態管理, React / Next.js) リファレンス。 useQueryState, useQueryStates, parseAsString / parseAsInteger / parseAsArrayOf 等 parsers、 NuqsAdapter (Next.js / React Router / TanStack Router / Remix)、createSerializer、 createStandardSchemaV1, inferParserType、shallow routing、history 制御、SSR、 URL 長さ制限 (limits)、Zod / Effect / Sury 連携。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.