dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-14 13:49:09 +03:00

Files

T

Alaister Young 1d4520a832 fix: adapt tests to vitest 4 breaking changes

- Use explicit mock factory for fs/promises (automocking no longer
  creates mock functions for getter-based exports on Node built-ins)
- Use function keyword instead of arrow functions in mockImplementation
  for mocks called with new (vitest 4 enforces constructor semantics)
- Fix ResizeObserver mock in ui-patterns setup for same reason

2026-04-14 11:42:48 +09:00

scripts

chore: Migrate studio to use ui-patterns/shimmeringLoader (#41405 )

2025-12-17 14:54:07 +01:00

src

fix: clean up grouped input border rendering (#44690 )

2026-04-10 12:03:23 +10:00

index.tsx

chore: Clean the ui package from next imports (#44278 )

2026-03-30 10:58:37 +02:00

package.json

chore: upgrade vite to v8 and vitest to v4

2026-04-14 11:42:37 +09: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: Bump Typescript to v6 (#44204 )

2026-03-26 15:27:35 +01:00

vitest.config.ts

add coverage option to ui-patterns (#35669 )

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

vitest.setup.ts

fix: adapt tests to vitest 4 breaking changes

2026-04-14 11:42:48 +09: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.