mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 02:45:07 +03:00
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Refactor, bug fix. Part 1 of 6 in a stack that splits the library redesign into reviewable pieces. This one is the foundation the rest build on and has no visual change. ## What is the current behavior? Three build steps each reimplement "where does this registry file land in the user's project": `process-registry`'s `getDefaultPath`, `registry/utils`' `uniqBy` on `file.path`, and the Markdown exporter. They disagree, which produces real bugs: - A Vue block whose files come from `node_modules/@supabase/vue-blocks/` keeps its package path, so the installer writes the package folder into the user's project. - `registryItemAppend` builds its `docs` string from `(item.docs, items.flatMap(...))` — a comma expression, so the item's own docs are discarded. - A name collision between a block file and its client's file silently keeps one of the two. - Install commands guess the CLI family from substrings in the item name, so `infinite-query-composable` — a Vue block with neither "vue" nor "nuxtjs" in its name — gets the React CLI. - Production Vue installs use `@supabase/<name>`, but the `@supabase` namespace is registered with shadcn, not shadcn-vue. - `build:registry`, `build:content`, `build:markdown` and `build:llms` run in parallel, but the last three read `public/r`. ## What is the new behavior? `lib/registry-resolution.ts` owns installed-path derivation, first-party dependency naming, deduplication, and cycle detection, and every consumer calls it. `build-registry` validates the whole registry against shadcn's schema and resolves every item, so a broken reference fails the build instead of shipping. `clean-registry` throws rather than logging past a failure. Pages declare their install `framework` explicitly instead of it being inferred, and production Vue installs use the absolute registry URL. The build steps are serialized behind `build:prepare`, and a new `library-tests.yml` workflow runs the library's tests, checks the generated registry is committed, and builds the app. ## Additional context Regenerated registry artifacts are the mechanical result of the resolution fix — the Vue client items and the OAuth consent items that gained their client's docs. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added explicit React and Vue framework selection for library blocks and installation commands. * Improved registry resolution, dependency handling, path validation, and Vue file normalization. * Added support for reliable local, preview, and production registry URLs. * **Documentation** * Updated Vue and Nuxt installation documentation to identify the Vue framework explicitly. * **Bug Fixes** * Preserved combined documentation and validated generated registry content more consistently. * **Tests** * Added coverage for installation commands, registry resolution, dependency handling, and generated artifacts. * **Chores** * Added automated pull-request checks for library tests and builds. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
130 lines
3.7 KiB
Plaintext
130 lines
3.7 KiB
Plaintext
---
|
|
title: Realtime Chat
|
|
description: Real-time chat component for collaborative applications
|
|
---
|
|
|
|
<DualRealtimeChat />
|
|
|
|
## Installation
|
|
|
|
<BlockItem
|
|
name="realtime-chat-nuxtjs"
|
|
description="Renders a real-time chat interface for users in a shared room."
|
|
framework="vue"
|
|
/>
|
|
|
|
## Folder structure
|
|
|
|
This block assumes that you have already installed a Supabase client for Vue from the previous step.
|
|
|
|
<RegistryBlock itemName="realtime-chat-nuxtjs" />
|
|
|
|
## Introduction
|
|
|
|
The Realtime Chat component provides a complete chat interface that enables users to exchange messages in real-time within a shared room.
|
|
|
|
## How it works under the hood
|
|
|
|
This chat component uses **Supabase Realtime Broadcast** to send and receive messages between connected clients.
|
|
|
|
Messages sent through Broadcast are:
|
|
|
|
- delivered in real time to other connected clients
|
|
- **not stored** unless you handle persistence yourself
|
|
- **not guaranteed** to arrive if the client disconnects
|
|
- scoped to a specific `roomName`, which corresponds to a broadcast channel
|
|
|
|
This design keeps latency extremely low, but it means you should use the `onMessage` callback if you want to store messages permanently or show chat history on page load.
|
|
|
|
## Usage
|
|
|
|
### Basic usage
|
|
|
|
```html
|
|
<script setup lang="ts">
|
|
import RealtimeChat from '@/components/realtime-chat.vue'
|
|
</script>
|
|
|
|
<template>
|
|
<RealtimeChat roomName="my-chat-room" username="john_doe" />
|
|
</template>
|
|
```
|
|
|
|
### With initial messages
|
|
|
|
```html
|
|
<script setup lang="ts">
|
|
import RealtimeChat from '@/components/realtime-chat.vue'
|
|
import { useMessagesQuery } from '@/composables/use-messages-query'
|
|
|
|
const { data } = useMessagesQuery()
|
|
</script>
|
|
|
|
<template>
|
|
<RealtimeChat roomName="my-chat-room" username="john_doe" :messages="data ?? []" />
|
|
</template>
|
|
```
|
|
|
|
### Storing messages
|
|
|
|
```html
|
|
<script setup lang="ts">
|
|
import RealtimeChat from '@/components/realtime-chat.vue'
|
|
import { useMessagesQuery } from '@/composables/use-messages-query'
|
|
import { storeMessages } from '@/lib/store-messages'
|
|
import type { ChatMessage } from '@/types'
|
|
|
|
const { data } = useMessagesQuery()
|
|
|
|
// Callback function for new messages
|
|
const handleMessage = async (messages: ChatMessage[]) => {
|
|
await storeMessages(messages)
|
|
}
|
|
</script>
|
|
|
|
<template>
|
|
<RealtimeChat
|
|
roomName="my-chat-room"
|
|
username="john_doe"
|
|
:messages="data ?? []"
|
|
:onMessage="handleMessage"
|
|
/>
|
|
</template>
|
|
```
|
|
|
|
## Features
|
|
|
|
- Real-time message synchronization
|
|
- Message persistence support with `onMessage` and `messages` props
|
|
- Customizable message appearance
|
|
- Automatic scroll-to-bottom on new messages
|
|
- Room-based isolation for scoped conversations
|
|
- Low-latency updates using Supabase Realtime
|
|
|
|
## Props
|
|
|
|
| Prop | Type | Description |
|
|
| ------------ | ----------------------------------- | ------------------------------------------------------------- |
|
|
| `roomName` | `string` | Unique identifier for the shared chat room. |
|
|
| `username` | `string` | Name of the current user; used to identify message senders. |
|
|
| `onMessage?` | `(messages: ChatMessage[]) => void` | Optional callback to handle messages, useful for persistence. |
|
|
| `messages?` | `ChatMessage[]` | Optional initial messages to display in the chat. |
|
|
|
|
### ChatMessage type
|
|
|
|
```typescript
|
|
interface ChatMessage {
|
|
id: string
|
|
content: string
|
|
user: {
|
|
name: string
|
|
}
|
|
createdAt: string
|
|
}
|
|
```
|
|
|
|
## Further reading
|
|
|
|
- [Realtime Broadcast](https://supabase.com/docs/guides/realtime/broadcast)
|
|
- [Realtime authorization](https://supabase.com/docs/guides/realtime/authorization)
|