mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
## Summary - `contentlayer2@0.4.6` is unmaintained and drags in a heavy, stale dependency graph (esbuild pinned to 0.17–0.20, mdx-bundler, old `@opentelemetry/core`) that was the recurring source of vuln bumps. - Migrates all three apps that used it — `design-system`, `ui-library`, `learn` — to [Velite](https://velite.js.org), preserving the generated typed `allDocs`/`Doc` collection and the `body.code` + `useMDXComponent` runtime via a small shared local hook. - Same MDX pipeline (remark-gfm, remark-code-import, rehype-slug, rehype-pretty-code w/ Shiki compat + local theme, rehype-autolink-headings, custom `__rawString__`/`__src__`/`__event__`/`__style__` visitors) ported 1:1 into each app's `velite.config.js`. - `learn`'s extra frontmatter fields (`chapterNumber`, `explore`, `courseHero`) are now backed by real Velite/Zod schema types, so the `(doc as any)` casts in `get-next-page.ts` / `get-current-chapter.ts` / the doc page could be dropped. - `next.config.mjs` no longer wraps with `withContentlayer`; since Velite has no Next.js webpack-plugin equivalent, each app's `dev` script now runs `velite dev` and `next dev` in parallel via `npm-run-all`. Ref: [FE-3861](https://linear.app/supabase/issue/FE-3861/migrate-off-contentlayer2-learn-ui-library-design-system-to-shed) ## Test plan - [x] `pnpm build:content` (Velite build) succeeds for all three apps - [x] `pnpm typecheck` passes for all three apps - [ ] Manual smoke test of `pnpm dev` for each app in a browser (docs pages render, TOC, copy-button, code highlighting) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Improvements** * Improved content generation across documentation, learning materials, and the UI library for more consistent pages. * Preserved MDX rendering, navigation, table of contents, course metadata, source previews, and component examples. * Improved consistency when displaying documentation and interactive examples. * Improved application loading by optimizing how interface components are delivered. * **Chores** * Streamlined content compilation and development workflows across the design system, learning area, and UI library. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
266 lines
6.0 KiB
Plaintext
266 lines
6.0 KiB
Plaintext
---
|
|
title: Carousel
|
|
description: A carousel with motion and swipe built using Embla.
|
|
component: true
|
|
links:
|
|
doc: https://www.embla-carousel.com/get-started/react
|
|
api: https://www.embla-carousel.com/api
|
|
---
|
|
|
|
## About
|
|
|
|
The carousel component is built using the [Embla Carousel](https://www.embla-carousel.com/) library.
|
|
|
|
## Installation
|
|
|
|
<Tabs defaultValue="cli">
|
|
|
|
<TabsList>
|
|
<TabsTrigger value="cli">CLI</TabsTrigger>
|
|
<TabsTrigger value="manual">Manual</TabsTrigger>
|
|
</TabsList>
|
|
|
|
<TabsContent value="cli">
|
|
|
|
```bash
|
|
npx shadcn-ui@latest add carousel
|
|
```
|
|
|
|
</TabsContent>
|
|
|
|
<TabsContent value="manual">
|
|
|
|
<Steps>
|
|
|
|
<Step>Install the following dependencies:</Step>
|
|
|
|
```bash
|
|
npm install embla-carousel-react
|
|
```
|
|
|
|
<Step>Copy and paste the following code into your project.</Step>
|
|
|
|
{/* <ComponentSource name="carousel" /> */}
|
|
|
|
<Step>Update the import paths to match your project setup.</Step>
|
|
|
|
</Steps>
|
|
|
|
</TabsContent>
|
|
|
|
</Tabs>
|
|
|
|
## Usage
|
|
|
|
```tsx
|
|
import {
|
|
Carousel,
|
|
CarouselContent,
|
|
CarouselItem,
|
|
CarouselNext,
|
|
CarouselPrevious,
|
|
} from '@/components/ui/carousel'
|
|
```
|
|
|
|
```tsx
|
|
<Carousel>
|
|
<CarouselContent>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
</CarouselContent>
|
|
<CarouselPrevious />
|
|
<CarouselNext />
|
|
</Carousel>
|
|
```
|
|
|
|
## Examples
|
|
|
|
### Sizes
|
|
|
|
To set the size of the items, you can use the `basis` utility class on the `<CarouselItem />`.
|
|
|
|
```tsx title="Example" showLineNumbers {4-6}
|
|
// 33% of the carousel width.
|
|
<Carousel>
|
|
<CarouselContent>
|
|
<CarouselItem className="basis-1/3">...</CarouselItem>
|
|
<CarouselItem className="basis-1/3">...</CarouselItem>
|
|
<CarouselItem className="basis-1/3">...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
```tsx title="Responsive" showLineNumbers {4-6}
|
|
// 50% on small screens and 33% on larger screens.
|
|
<Carousel>
|
|
<CarouselContent>
|
|
<CarouselItem className="md:basis-1/2 lg:basis-1/3">...</CarouselItem>
|
|
<CarouselItem className="md:basis-1/2 lg:basis-1/3">...</CarouselItem>
|
|
<CarouselItem className="md:basis-1/2 lg:basis-1/3">...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
### Spacing
|
|
|
|
To set the spacing between the items, we use a `pl-[VALUE]` utility on the `<CarouselItem />` and a negative `-ml-[VALUE]` on the `<CarouselContent />`.
|
|
|
|
<Callout className="mt-6">
|
|
**Why:** I tried to use the `gap` property or a `grid` layout on the `
|
|
<CarouselContent />` but it required a lot of math and mental effort to get the
|
|
spacing right. I found `pl-[VALUE]` and `-ml-[VALUE]` utilities much easier to
|
|
use.
|
|
|
|
You can always adjust this in your own project if you need to.
|
|
|
|
</Callout>
|
|
|
|
```tsx title="Example" showLineNumbers /-ml-4/ /pl-4/
|
|
<Carousel>
|
|
<CarouselContent className="-ml-4">
|
|
<CarouselItem className="pl-4">...</CarouselItem>
|
|
<CarouselItem className="pl-4">...</CarouselItem>
|
|
<CarouselItem className="pl-4">...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
```tsx title="Responsive" showLineNumbers /-ml-2/ /pl-2/ /md:-ml-4/ /md:pl-4/
|
|
<Carousel>
|
|
<CarouselContent className="-ml-2 md:-ml-4">
|
|
<CarouselItem className="pl-2 md:pl-4">...</CarouselItem>
|
|
<CarouselItem className="pl-2 md:pl-4">...</CarouselItem>
|
|
<CarouselItem className="pl-2 md:pl-4">...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
### Orientation
|
|
|
|
Use the `orientation` prop to set the orientation of the carousel.
|
|
|
|
```tsx showLineNumbers /vertical | horizontal/
|
|
<Carousel orientation="vertical | horizontal">
|
|
<CarouselContent>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
## Options
|
|
|
|
You can pass options to the carousel using the `opts` prop. See the [Embla Carousel docs](https://www.embla-carousel.com/api/options/) for more information.
|
|
|
|
```tsx showLineNumbers {2-5}
|
|
<Carousel
|
|
opts={{
|
|
align: 'start',
|
|
loop: true,
|
|
}}
|
|
>
|
|
<CarouselContent>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
```
|
|
|
|
## API
|
|
|
|
Use a state and the `setApi` props to get an instance of the carousel API.
|
|
|
|
```tsx showLineNumbers {1,4,22}
|
|
import { type CarouselApi } from '@/components/ui/carousel'
|
|
|
|
export function Example() {
|
|
const [api, setApi] = React.useState<CarouselApi>()
|
|
const [current, setCurrent] = React.useState(0)
|
|
const [count, setCount] = React.useState(0)
|
|
|
|
React.useEffect(() => {
|
|
if (!api) {
|
|
return
|
|
}
|
|
|
|
setCount(api.scrollSnapList().length)
|
|
setCurrent(api.selectedScrollSnap() + 1)
|
|
|
|
api.on('select', () => {
|
|
setCurrent(api.selectedScrollSnap() + 1)
|
|
})
|
|
}, [api])
|
|
|
|
return (
|
|
<Carousel setApi={setApi}>
|
|
<CarouselContent>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
)
|
|
}
|
|
```
|
|
|
|
## Events
|
|
|
|
You can listen to events using the api instance from `setApi`.
|
|
|
|
```tsx showLineNumbers {1,4-14,16}
|
|
import { type CarouselApi } from '@/components/ui/carousel'
|
|
|
|
export function Example() {
|
|
const [api, setApi] = React.useState<CarouselApi>()
|
|
|
|
React.useEffect(() => {
|
|
if (!api) {
|
|
return
|
|
}
|
|
|
|
api.on('select', () => {
|
|
// Do something on select.
|
|
})
|
|
}, [api])
|
|
|
|
return (
|
|
<Carousel setApi={setApi}>
|
|
<CarouselContent>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
<CarouselItem>...</CarouselItem>
|
|
</CarouselContent>
|
|
</Carousel>
|
|
)
|
|
}
|
|
```
|
|
|
|
See the [Embla Carousel docs](https://www.embla-carousel.com/api/events/) for more information on using events.
|
|
|
|
## Plugins
|
|
|
|
You can use the `plugins` prop to add plugins to the carousel.
|
|
|
|
```ts showLineNumbers {1,6-10}
|
|
import Autoplay from "embla-carousel-autoplay"
|
|
|
|
export function Example() {
|
|
return (
|
|
<Carousel
|
|
plugins={[
|
|
Autoplay({
|
|
delay: 2000,
|
|
}),
|
|
]}
|
|
>
|
|
// ...
|
|
</Carousel>
|
|
)
|
|
}
|
|
```
|
|
|
|
See the [Embla Carousel docs](https://www.embla-carousel.com/api/plugins/) for more information on using plugins.
|