Skip to content

Commit 8912ed8

Browse files
shinokadashinokada
committed
chore: dependencies update
1 parent 7ccf086 commit 8912ed8

File tree

5 files changed

+205
-3
lines changed

5 files changed

+205
-3
lines changed

‎CHANGELOG.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
# Changelog
22

3+
## 1.30.1
4+
5+
### Patch Changes
6+
7+
- fix:mcp overview update
8+
- feat: Add data attributes for selected and active items in MulitSelect
9+
- fix: Move createSingleSelectionContext(multiple) out of the $effect() and call it synchronously during component initialization
10+
- fix: Added import statement: import { untrack } from "svelte" to each file (or modified existing imports from svelte to include untrack)
11+
- fix: Removed comment line: Deleted the // svelte-ignore state_referenced_locally comment
12+
- fix: Wrapped object in untrack: Changed the second parameter of warnThemeDeprecation from a plain object to untrack(() => ({ ... }))
13+
314
## 1.30.0
415

516
### Minor Changes

‎package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "flowbite-svelte",
3-
"version": "1.30.0",
3+
"version": "1.30.1",
44
"description": "Flowbite components for Svelte",
55
"main": "dist/index.js",
66
"author": {
@@ -915,4 +915,4 @@
915915
},
916916
"./package.json": "./package.json"
917917
}
918-
}
918+
}

‎src/routes/llm/context-full.txt‎

Lines changed: 81 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Flowbite Svelte Documentation - Full Context
2-
# Generated on 2025-12-06T06:41:40.349Z
2+
# Generated on 2025-12-11T12:52:21.046Z
33
# This file contains all documentation concatenated in logical order
44

55

@@ -31366,6 +31366,86 @@ Performs full-text search across all Flowbite-Svelte documentation.
3136631366
Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns.
3136731367
```
3136831368

31369+
## CLAUDE.md for Svelte and Flowbite-Svelte
31370+
31371+
Use the following example for Svelte and Flowbite-Svelte:
31372+
```md
31373+
# Claude MCP Server Documentation
31374+
31375+
This project uses multiple MCP servers to provide comprehensive documentation access.
31376+
31377+
## Available MCP Servers
31378+
31379+
### Svelte MCP Server
31380+
31381+
You have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
31382+
31383+
#### Available Tools:
31384+
31385+
**1. list-sections**
31386+
- Use this FIRST to discover all available documentation sections
31387+
- Returns a structured list with titles, use_cases, and paths
31388+
- When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start to find relevant sections
31389+
31390+
**2. get-documentation**
31391+
- Retrieves full documentation content for specific sections
31392+
- Accepts single or multiple sections
31393+
- After calling list-sections, you MUST analyze the returned documentation (especially the use_cases field) and then fetch ALL relevant sections for the user's task
31394+
31395+
**3. svelte-autofixer**
31396+
- Analyzes Svelte code and returns issues and suggestions
31397+
- You MUST use this tool whenever writing Svelte code before sending it to the user
31398+
- Keep calling it until no issues or suggestions are returned
31399+
31400+
**4. playground-link**
31401+
- Generates a Svelte Playground link with the provided code
31402+
- After completing the code, ask the user if they want a playground link
31403+
- NEVER call this if code was written to files in their project
31404+
31405+
### Flowbite-Svelte MCP Server
31406+
31407+
You have access to comprehensive Flowbite-Svelte component documentation. Here's how to use the available tools effectively:
31408+
31409+
#### Available Tools:
31410+
31411+
**1. findComponent**
31412+
- Use this FIRST to discover components by name or category
31413+
- Returns component information including the documentation path
31414+
- When asked about Flowbite-Svelte components, ALWAYS use this tool to locate the correct component before fetching documentation
31415+
- Example queries: 'Button', 'CardPlaceholder', 'form checkbox'
31416+
31417+
**2. getComponentList**
31418+
- Lists all available Flowbite-Svelte components with their categories
31419+
- Use this to discover what components are available or to help users explore component options
31420+
31421+
**3. getComponentDoc**
31422+
- Retrieves full documentation content for a specific component
31423+
- Accepts the component path found using findComponent
31424+
- After calling findComponent, use this tool to fetch complete documentation including usage examples, props, and best practices
31425+
31426+
**4. searchDocs**
31427+
- Performs full-text search across all Flowbite-Svelte documentation
31428+
- Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns
31429+
31430+
## Workflow Guidelines
31431+
31432+
### When building Svelte components with Flowbite-Svelte:
31433+
31434+
1. **Start with Svelte documentation**: Use `list-sections` to understand which Svelte concepts are needed
31435+
2. **Fetch relevant Svelte docs**: Use `get-documentation` to get all necessary Svelte sections
31436+
3. **Find Flowbite-Svelte components**: Use `findComponent` to locate the UI components needed
31437+
4. **Get component details**: Use `getComponentDoc` to fetch usage examples and props
31438+
5. **Write the code**: Combine Svelte patterns with Flowbite-Svelte components
31439+
6. **Validate the code**: Use `svelte-autofixer` to check for issues
31440+
7. **Offer playground**: Ask if the user wants a playground link (only if not writing to files)
31441+
31442+
### Best Practices:
31443+
31444+
- Always prioritize Svelte 5 runes and modern patterns
31445+
- Use Flowbite-Svelte components for consistent UI design
31446+
- Validate all code with svelte-autofixer before delivering
31447+
- Keep documentation lookups efficient by fetching multiple sections at once
31448+
```
3136931449

3137031450
---
3137131451

‎src/routes/llm/mcp/overview.md‎

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,3 +35,84 @@ After calling findComponent, use this tool to fetch the complete documentation i
3535
Performs full-text search across all Flowbite-Svelte documentation.
3636
Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns.
3737
```
38+
39+
## CLAUDE.md for Svelte and Flowbite-Svelte
40+
41+
Use the following example for Svelte and Flowbite-Svelte:
42+
```md
43+
# Claude MCP Server Documentation
44+
45+
This project uses multiple MCP servers to provide comprehensive documentation access.
46+
47+
## Available MCP Servers
48+
49+
### Svelte MCP Server
50+
51+
You have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
52+
53+
#### Available Tools:
54+
55+
**1. list-sections**
56+
- Use this FIRST to discover all available documentation sections
57+
- Returns a structured list with titles, use_cases, and paths
58+
- When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start to find relevant sections
59+
60+
**2. get-documentation**
61+
- Retrieves full documentation content for specific sections
62+
- Accepts single or multiple sections
63+
- After calling list-sections, you MUST analyze the returned documentation (especially the use_cases field) and then fetch ALL relevant sections for the user's task
64+
65+
**3. svelte-autofixer**
66+
- Analyzes Svelte code and returns issues and suggestions
67+
- You MUST use this tool whenever writing Svelte code before sending it to the user
68+
- Keep calling it until no issues or suggestions are returned
69+
70+
**4. playground-link**
71+
- Generates a Svelte Playground link with the provided code
72+
- After completing the code, ask the user if they want a playground link
73+
- NEVER call this if code was written to files in their project
74+
75+
### Flowbite-Svelte MCP Server
76+
77+
You have access to comprehensive Flowbite-Svelte component documentation. Here's how to use the available tools effectively:
78+
79+
#### Available Tools:
80+
81+
**1. findComponent**
82+
- Use this FIRST to discover components by name or category
83+
- Returns component information including the documentation path
84+
- When asked about Flowbite-Svelte components, ALWAYS use this tool to locate the correct component before fetching documentation
85+
- Example queries: 'Button', 'CardPlaceholder', 'form checkbox'
86+
87+
**2. getComponentList**
88+
- Lists all available Flowbite-Svelte components with their categories
89+
- Use this to discover what components are available or to help users explore component options
90+
91+
**3. getComponentDoc**
92+
- Retrieves full documentation content for a specific component
93+
- Accepts the component path found using findComponent
94+
- After calling findComponent, use this tool to fetch complete documentation including usage examples, props, and best practices
95+
96+
**4. searchDocs**
97+
- Performs full-text search across all Flowbite-Svelte documentation
98+
- Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns
99+
100+
## Workflow Guidelines
101+
102+
### When building Svelte components with Flowbite-Svelte:
103+
104+
1. **Start with Svelte documentation**: Use `list-sections` to understand which Svelte concepts are needed
105+
2. **Fetch relevant Svelte docs**: Use `get-documentation` to get all necessary Svelte sections
106+
3. **Find Flowbite-Svelte components**: Use `findComponent` to locate the UI components needed
107+
4. **Get component details**: Use `getComponentDoc` to fetch usage examples and props
108+
5. **Write the code**: Combine Svelte patterns with Flowbite-Svelte components
109+
6. **Validate the code**: Use `svelte-autofixer` to check for issues
110+
7. **Offer playground**: Ask if the user wants a playground link (only if not writing to files)
111+
112+
### Best Practices:
113+
114+
- Always prioritize Svelte 5 runes and modern patterns
115+
- Use Flowbite-Svelte components for consistent UI design
116+
- Validate all code with svelte-autofixer before delivering
117+
- Keep documentation lookups efficient by fetching multiple sections at once
118+
```

‎workflow.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
2+
```sh
3+
git fetch origin --tags # Fetch latest tags
4+
pnpm ch
5+
pnpm cv
6+
pnpm lib-helpers
7+
pnpm cp
8+
git add .
9+
git commit --message 'v1.x.x'
10+
git push origin main # Push your commits
11+
git push origin --tags # Push your new tag
12+
At https://github.com/themesberg/flowbite-svelte/releases publish a new version
13+
```
14+
15+
## Checking tags
16+
Always use version sorting when checking tags
17+
18+
```sh
19+
git tag --list | sort -V | tail -n 20
20+
```
21+
22+
## Alias
23+
Check if this works:
24+
```sh
25+
git tags | tail -n 20
26+
```
27+
If not create an alias:
28+
```sh
29+
git config --global alias.tags '!git tag -l | sort -V'
30+
```

0 commit comments

Comments
 (0)