We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to spawn the command palette. I tried wrapping it into a 'use client' component but the issue keeps happening.
Dependencies:
Error: Invariant failed: Input ref is undefined, make sure you attach `query.inputRefSetter` to your search input. Call Stack invariant node_modules/tiny-invariant/dist/tiny-invariant.cjs.js (14:1) Object.getInput node_modules/kbar/lib/useStore.js (107:1) handler node_modules/kbar/lib/InternalEvents.js (277:1)
The text was updated successfully, but these errors were encountered:
did you manage to solve this?
Sorry, something went wrong.
For me adding use client at the top of the provider ( which is them added to my root layout ) is yielding another error.
use client
// KBarProvider.ts 'use client' import { KBarAnimator, KBarPortal, KBarPositioner, KBarProvider as OriginalKBarProvider, KBarSearch } from 'kbar' import type { ReactNode } from 'react' interface Props { children: ReactNode } const KBarProvider = ({ children }: Props) => { return ( <OriginalKBarProvider> <KBarPortal> <KBarPositioner> <KBarAnimator> <KBarSearch /> {/* <KBarResults /> */} </KBarAnimator> </KBarPositioner> </KBarPortal> {children} </OriginalKBarProvider> ) } export default KBarProvider
The error i get is:
Caution
TypeError: createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component
No branches or pull requests
Fails to spawn the command palette.
I tried wrapping it into a 'use client' component but the issue keeps happening.
Dependencies:
The text was updated successfully, but these errors were encountered: