dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-12 21:05:06 +03:00

Files

T

Danny White ac1006fc1a chore(design-system): admonition background fill (#39474 )

* add colour to admonition

* clarify design docs

* remove old references to alert

* better docs

* remove redundant className

* consolidate colors

* improve docs

* restore alert

* remove unrelated work

2025-12-05 02:11:16 +00:00

scripts

chore: Move the files in ui-patterns under src folder (#36032 )

2025-05-30 12:46:22 +03:00

src

chore(design-system): admonition background fill (#39474 )

2025-12-05 02:11:16 +00:00

index.tsx

chore(studio): empty state improvements (#40807 )

2025-11-27 17:26:20 +08:00

package.json

Review Supabase MCP config on existing clients and add more clients support (#40525 )

2025-11-26 19:36:19 +00:00

README.md

feat: Move some components into ui-patterns (#20774 )

2024-02-12 12:44:00 +01:00

tailwind.config.js

SQL to REST translator (#25978 )

2024-05-22 12:37:01 -06:00

tsconfig.json

chore: Move the files in ui-patterns under src folder (#36032 )

2025-05-30 12:46:22 +03:00

vitest.config.ts

add coverage option to ui-patterns (#35669 )

2025-05-29 19:09:26 +02:00

vitest.setup.ts

Improves the filter bar (#38389 )

2025-09-09 20:06:25 +02:00

README.md

Supabase UI Patterns

This package should be used for components which are built using NPM libraries (react-markdown, reactflow for example), which make no sense to be included in all apps. It should also be used for components which are constructed using various components from the ui package.

This package does not have a barrel file - each component has to be imported from its index (ui-patterns/PrivacySettings, for example). This is intentional so that adding a new component which is used only in 1 or 2 apps doesn't burden the rest of the apps.