<!--<p align="center"> <img src="./website/public/og.png" /> </p>-->
npm install cmdk-solid⌘K is a command menu SolidJS component that can also be used as an accessible combobox. You render items, it filters and sorts them automatically. ⌘K supports a fully composable API, so you can wrap items in other components or even as static JSX.
⌘K is a port for SolidJS of pacocoursey's wonderful CMDK component.
Every attempt was made to make the behavior identical. The most notable difference is the inclusion of Kobalte to provide Dialog boxes which has a slightly different API to RadixUI.
Demo and examples: https://cmdk-solid.vercel.app/
``bash`
pnpm install cmdk-solid
`tsx
import { Command } from 'cmdk-solid'
const CommandMenu = () => {
return (
)
}
`
Or in a dialog:
`tsx
import { Command } from 'cmdk-solid'
const CommandMenu = () => {
const [open, setOpen] = createSignal(false)
// Toggle the menu when ⌘K is pressed
onMount(() => {
const down = (e: KeyboardEvent) => {
if (e.key === 'k' && (e.metaKey || e.ctrlKey)) {
e.preventDefault()
setOpen((open) => !open)
}
}
document.addEventListener('keydown', down)
onCleanup(() => document.removeEventListener('keydown', down))
})
return (
)
}
`
All parts forward props, including ref, to an appropriate element. Each part has a specific data-attribute (starting with cmdk-) that can be used for styling.
Render this to show the command menu inline, or use Dialog to render in a elevated context. Can be controlled with the value and onValueChange props.
> Note
>
> Values are always trimmed with the trim() method.
`tsx
const [value, setValue] = createSignal('apple')
return (
)
`
You can provide a custom filter function that is called to rank each item. Note that the value will be trimmed.
`tsx`
if (value.includes(search)) return 1
return 0
}}
/>
A third argument, keywords, can also be provided to the filter function. Keywords act as aliases for the item value, and can also affect the rank of the item. Keywords are trimmed.
`tsx`
const extendValue = value + ' ' + keywords.join(' ')
if (extendValue.includes(search)) return 1
return 0
}}
/>
Or disable filtering and sorting entirely:
`tsx`
You can make the arrow keys wrap around the list (when you reach the end, it goes back to the first item) by setting the loop prop:
`tsx`
Props are forwarded to Command. Composes Kobalte's Dialog component. The overlay is always rendered. See the Kobalte Documentation for more information. Can be controlled with the open and onOpenChange props.
`tsx
const [open, setOpen] = createSignal(false)
return (
...
)
`
You can provide a container prop that accepts an HTML element that is forwarded to Kobalte's Dialog Portal component to specify which element the Dialog should portal into (defaults to body). See the SolidJS Documentation for more information.
`tsx
let containerElement: HTMLDivElement | undefined
return (
<>
$3
All props are forwarded to the underlying
element. Can be controlled with the value and onValueChange props.`tsx
const [search, setSearch] = createSignal('')return
`$3
Contains items and groups. Animate height using the
CSS variable.`css
[cmdk-list] {
min-height: 300px;
height: var(--cmdk-list-height);
max-height: 500px;
transition: height 100ms ease;
}
`To scroll item into view earlier near the edges of the viewport, use scroll-padding:
css
[cmdk-list] {
scroll-padding-block-start: 8px;
scroll-padding-block-end: 8px;
}
`$3
Item that becomes active on pointer enter. You should provide a unique
for each item, but it will be automatically inferred from the .textContent.`tsx
// Value is implicity "apple" because of the provided text content
>
Apple
`You can also provide a
prop to help with filtering. Keywords are trimmed.`tsx
Apple
`tsx
// Value is implicity "apple" because of the provided text content
>
Apple
`You can force an item to always render, regardless of filtering, by passing the
prop.$3
Groups items together with the given
heading ([cmdk-group-heading]).`tsx
Apple
`Groups will not unmount from the DOM, rather the
attribute is applied to hide it from view. This may be relevant in your styling.You can force a group to always render, regardless of filtering, by passing the
forceMount prop.$3
Visible when the search query is empty or
alwaysRender is true, hidden otherwise.$3
Automatically renders when there are no results for the search query.
$3
You should conditionally render this with
progress while loading asynchronous items.`tsx
const [loading, setLoading] = createSignal(false)return (
Hang on…
)
`$3
Hook that can return a slice of the command menu state to re-render when that slice changes. This hook is provided for advanced use cases and should not be commonly used.
A good use case would be to render a more detailed empty state, like so:
tsx
const search = useCommandState((state) => state.search)
return No results found for "{search()}".
`Examples
Code snippets for common use cases.
$3
Often selecting one item should navigate deeper, with a more refined set of items. For example selecting "Change theme…" should show new items "Dark theme" and "Light theme". We call these sets of items "pages", and they can be implemented with simple state:
tsx
const [search, setSearch] = createSignal('')
const [pages, setPages] = createSignal([])
const page = () => pages()[pages().length - 1]return (
// Escape goes to previous page
// Backspace goes to previous page when search is empty
if (e.key === 'Escape' || (e.key === 'Backspace' && !search())) {
e.preventDefault()
setPages((pages) => pages.slice(0, -1))
}
}}
>
setPages([...pages(), 'projects'])}>Search projects…
setPages([...pages(), 'teams'])}>Join a team…
Project A
Project B
Team 1
Team 2
)
`$3
If your items have nested sub-items that you only want to reveal when searching, render based on the search state:
tsx
const SubItem = (props: CommandItemProps) => {
const search = useCommandState(state => state.search)
return (
)
} return (
Change theme…
Change theme to dark
Change theme to light
)
}
`$3
Render the items as they become available. Filtering and sorting will happen automatically.
tsx
const [loading, setLoading] = createSignal(false)
const [items, setItems] = createSignal([])onMount(() => {
async function getItems() {
setLoading(true)
const res = await asyncResource()
setItems(res)
setLoading(false)
}
getItems()
})
return (
Fetching words…
{(item) => {item} }
)
`$3
We recommend using the Kobalte popover component. ⌘K relies on the Kobalte Dialog component, so this will reduce your bundle size a bit due to shared dependencies.
bash
$ pnpm install @kobalte/core
`Render
inside of the popover content:`tsx
import { Popover } from '@kobalte/core'return (
Toggle popover
Apple
)
`$3
You can find global stylesheets to drop in as a starting point for styling. See website/src/styles/cmdk for examples.
FAQ
Accessible? Yes. Labeling, aria attributes, and DOM ordering tested with Voice Over and Chrome DevTools. Dialog composes an accessible Dialog implementation.
Virtualization? Performance has not been thoroughly tested. If you experience problems with performance with less than 2,000 items create a github issue. You can also roll your own virtualisation using the shouldFilter property.
Filter/sort items manually? Yes. Pass
to Command. Better memory usage and performance. Bring your own virtualization this way.Unstyled? Yes, use the listed CSS selectors.
Hydration mismatch? This may be a bug in your code. Feel free to create an issue in this repo if you are sure it is not.
Weird/wrong behavior? Make sure your
Command.Item has a unique value.Solid Start server component? Solid Start is still in beta. On the server this component renders a full list and then applies filtering and sorting when hydration is completed.
Listen for ⌘K automatically? No, do it yourself to have full control over keybind context.
History
Refer to the original repo for the history of CMDK.
Testing
First, install dependencies and Playwright browsers:
`bash
pnpm install
pnpm playwright install
`Then ensure you've built the library:
bash
pnpm build
`Then run the tests using your local build against real browser engines:
bash
pnpm test
``