mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 20:05:06 +03:00
Alaister Young
5988f92b53
The card pulls in @ai-sdk/react, the ai package, and the AIAssistantPanel Message subgraph. Statically importing it from SupportSidebarForm exposed that subgraph through the HelpPanel dynamic chunk in addition to the existing AIAssistant dynamic chunk, ballooning webpack's chunk-splitting work and pushing Vercel builds past their memory ceiling. It's flag-gated and only rendered after a ticket is submitted, so a static import was never justified.
Writing components
Where to create your components
- For components that declare the general structure and layout of a page:
/components/layouts/xxx
- For components that are tightly coupled to a specific interface:
/components/interfaces/xxx
- For components that are meant to be reusable across multiple pages:
/components/ui/xxx
- Note: We're gradually moving files out of the
to-be-cleanedfolder into the respective folders as we refactor
Component structure
- If a component has constants and utility methods that are tightly coupled to itself, keep them close to the component and enclose them in a folder with an
index.tsxas an entry point - Otherwise it can just be a file on its own
- For example:
-
components/ui - SampleComponentA - SampleComponentA.tsx - SampleComponentA.constants.ts - SampleComponentA.utils.ts - SampleComponentA.types.ts - index.ts - SampleComponentB.tsx
-
Template for building components
// Declare the prop types of your component
interface ComponentAProps {
sampleProp: string
}
// Name your component accordingly
const ComponentA = ({ sampleProp }: ComponentAProps) => {
return <div>ComponentA: {sampleProp}</div>
}
export default ComponentA