[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-3442":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":35,"readmeContent":36,"aiSummary":37,"trendingCount":16,"starSnapshotCount":16,"syncStatus":38,"lastSyncTime":39,"discoverSource":40},3442,"downshift","downshift-js\u002Fdownshift","downshift-js","🏎 A set of primitives to build simple, flexible, WAI-ARIA compliant React autocomplete, combobox or select dropdown components.","http:\u002F\u002Fdownshift-js.com\u002F",null,"JavaScript",12295,939,76,46,0,3,6,1,43.92,"MIT License",false,"master",[25,26,27,28,29,30,31,32,33,34],"accessible","autocomplete","autoselect","autosuggest","combobox","dropdown","multiselect","react","select","wai-aria","2026-06-12 02:00:50","\u003Ch1 align=\"center\">\n downshift 🏎\n \u003Cbr>\n \u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fdownshift-js\u002Fdownshift\u002Fmaster\u002Fother\u002Fpublic\u002Flogo\u002Fdownshift.svg\" alt=\"downshift logo\" title=\"downshift logo\" width=\"300\">\n \u003Cbr>\n\u003C\u002Fh1>\n\u003Cp align=\"center\" style=\"font-size: 1.2rem;\">Primitives to build simple, flexible, WAI-ARIA compliant React\nautocomplete, combobox or select dropdown components.\u003C\u002Fp>\n\n> [Read the docs](https:\u002F\u002Fdownshift-js.com) |\n> [See the intro blog post](https:\u002F\u002Fkentcdodds.com\u002Fblog\u002Fintroducing-downshift-for-react)\n> |\n> [Listen to the Episode 79 of the Full Stack Radio podcast](https:\u002F\u002Ffullstackradio.com\u002F79)\n\n\u003Chr \u002F>\n\n[![Build Status][build-badge]][build]\n[![Code Coverage][coverage-badge]][coverage]\n[![downloads][downloads-badge]][npmcharts] [![version][version-badge]][package]\n[![MIT License][license-badge]][license]\n\n[![All Contributors](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fall_contributors-113-orange.svg?style=flat-square)](#contributors)\n[![PRs Welcome][prs-badge]][prs] [![Chat][chat-badge]][chat]\n[![Code of Conduct][coc-badge]][coc]\n[![Join the community on Spectrum][spectrum-badge]][spectrum]\n\n[![Supports React and Preact][react-badge]][react]\n[![size][size-badge]][unpkg-dist] [![gzip size][gzip-badge]][unpkg-dist]\n[![module formats: umd, cjs, and es][module-formats-badge]][unpkg-dist]\n\n## The problem\n\nYou need an autocomplete, a combobox or a select experience in your application\nand you want it to be accessible. You also want it to be simple and flexible to\naccount for your use cases. Finally, it should follow the [ARIA][aria] design\npattern for a [combobox][combobox-aria-example] or a\n[select][select-aria-example], depending on your use case.\n\n## This solution\n\nThe library offers a couple of solutions. The first solution, which is the one\nwe recommend you to try first, is a set of React hooks. Each hook provides the\nstateful logic needed to make the corresponding component functional and\naccessible. Navigate to the documentation for each by using the links in the\nlist below.\n\n- [useSelect][useselect-readme] for a custom select component.\n- [useCombobox][combobox-readme] for a combobox or autocomplete input.\n- [useTagGroup][tag-group-readme] for a tag group component. Also useful to\n build a multiple selection combobox or select component with tags.\n\nThe second solution is the `Downshift` component, which can also be used to\ncreate accessible combobox and select components, providing the logic in the\nform of a render prop. It served as inspiration for developing the hooks and it\nhas been around for a while. It established a successful pattern for making\ncomponents accessible and functional while giving developers complete freedom\nwhen building the UI.\n\nBoth _useSelect_ and _useCombobox_ support the latest ARIA combobox patterns for\nW3C, which _Downshift_ does not. Consequently, we strongly recommend the you use\nthe hooks. The hooks have been migrated to the ARIA 1.2 combobox pattern in the\nversion 7 of _downshift_. There is a [Migration Guide][migration-guide-v7] that\ndocuments the changes introduced in version 7.\n\nThe `README` on this page covers only the component while each hook has its own\n`README` page. You can navigate to the [hooks page][hooks-readme] or go directly\nto the hook you need by using the links in the list above.\n\nFor examples on how to use the hooks or the Downshift component, check out our\n[docsite][docsite]!\n\n**🚨 Use the Downshift hooks 🚨**\n\nIf you are new to the library, consider the _useSelect_ and _useCombobox_ hooks\nas the first option. As mentioned above, the hooks benefit from the updated ARIA\npatterns and are actively maintained and improved. If there are use cases that\nare supported by the _Downshift_ component and not by the hooks, please create\nan issue in our repo. The _Downshift_ component is going to be removed\ncompletely once the hooks become mature.\n\n### Downshift\n\nThis is a component that controls user interactions and state for you so you can\ncreate autocomplete, combobox or select dropdown components. It uses a [render\nprop][use-a-render-prop] which gives you maximum flexibility with a minimal API\nbecause you are responsible for the rendering of everything and you simply apply\nprops to what you're rendering.\n\nThis differs from other solutions which render things for their use case and\nthen expose many options to allow for extensibility resulting in a bigger API\nthat is less flexible as well as making the implementation more complicated and\nharder to contribute to.\n\n> NOTE: The original use case of this component is autocomplete, however the API\n> is powerful and flexible enough to build things like dropdowns as well.\n\n## Table of Contents\n\n\u003C!-- START doctoc generated TOC please keep comment here to allow auto update -->\n\u003C!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->\n\n- [Installation](#installation)\n- [Usage](#usage)\n- [Basic Props](#basic-props)\n - [children](#children)\n - [itemToString](#itemtostring)\n - [onChange](#onchange)\n - [stateReducer](#statereducer)\n- [Advanced Props](#advanced-props)\n - [initialSelectedItem](#initialselecteditem)\n - [initialInputValue](#initialinputvalue)\n - [initialHighlightedIndex](#initialhighlightedindex)\n - [initialIsOpen](#initialisopen)\n - [defaultHighlightedIndex](#defaulthighlightedindex)\n - [defaultIsOpen](#defaultisopen)\n - [selectedItemChanged](#selecteditemchanged)\n - [getA11yStatusMessage](#geta11ystatusmessage)\n - [onSelect](#onselect)\n - [onStateChange](#onstatechange)\n - [onInputValueChange](#oninputvaluechange)\n - [itemCount](#itemcount)\n - [highlightedIndex](#highlightedindex)\n - [inputValue](#inputvalue)\n - [isOpen](#isopen)\n - [selectedItem](#selecteditem)\n - [id](#id)\n - [inputId](#inputid)\n - [labelId](#labelid)\n - [menuId](#menuid)\n - [getItemId](#getitemid)\n - [environment](#environment)\n - [onOuterClick](#onouterclick)\n - [scrollIntoView](#scrollintoview)\n- [stateChangeTypes](#statechangetypes)\n- [Control Props](#control-props)\n- [Children Function](#children-function)\n - [prop getters](#prop-getters)\n - [actions](#actions)\n - [state](#state)\n - [props](#props)\n- [Event Handlers](#event-handlers)\n - [default handlers](#default-handlers)\n - [customizing handlers](#customizing-handlers)\n- [Utilities](#utilities)\n - [resetIdCounter](#resetidcounter)\n- [React Native](#react-native)\n - [Gotchas](#gotchas)\n- [Advanced React Component Patterns course](#advanced-react-component-patterns-course)\n- [Examples](#examples)\n- [FAQ](#faq)\n- [Inspiration](#inspiration)\n- [Other Solutions](#other-solutions)\n- [Bindings for ReasonML](#bindings-for-reasonml)\n- [Contributors](#contributors)\n- [LICENSE](#license)\n\n\u003C!-- END doctoc generated TOC please keep comment here to allow auto update -->\n\n## Installation\n\nThis module is distributed via [npm][npm] which is bundled with [node][node] and\nshould be installed as one of your project's `dependencies`:\n\n```\nnpm install --save downshift\n```\n\n> This package also depends on `react`. Please make sure you have it installed\n> as well.\n\n> Note also this library supports `preact` out of the box. If you are using\n> `preact` then use the corresponding module in the `preact\u002Fdist` folder. You\n> can even `import Downshift from 'downshift\u002Fpreact'` 👍\n\n## Usage\n\n> [Try it out in the browser][code-sandbox-try-it-out]\n\n```jsx\nimport * as React from 'react'\nimport {render} from 'react-dom'\nimport Downshift from 'downshift'\n\nconst items = [\n {value: 'apple'},\n {value: 'pear'},\n {value: 'orange'},\n {value: 'grape'},\n {value: 'banana'},\n]\n\nrender(\n \u003CDownshift\n onChange={selection =>\n alert(selection ? `You selected ${selection.value}` : 'Selection Cleared')\n }\n itemToString={item => (item ? item.value : '')}\n >\n {({\n getInputProps,\n getItemProps,\n getLabelProps,\n getMenuProps,\n isOpen,\n inputValue,\n highlightedIndex,\n selectedItem,\n getRootProps,\n }) => (\n \u003Cdiv>\n \u003Clabel {...getLabelProps()}>Enter a fruit\u003C\u002Flabel>\n \u003Cdiv\n style={{display: 'inline-block'}}\n {...getRootProps({}, {suppressRefError: true})}\n >\n \u003Cinput {...getInputProps()} \u002F>\n \u003C\u002Fdiv>\n \u003Cul {...getMenuProps()}>\n {isOpen\n ? items\n .filter(item => !inputValue || item.value.includes(inputValue))\n .map((item, index) => (\n \u003Cli\n {...getItemProps({\n key: item.value,\n index,\n item,\n style: {\n backgroundColor:\n highlightedIndex === index ? 'lightgray' : 'white',\n fontWeight: selectedItem === item ? 'bold' : 'normal',\n },\n })}\n >\n {item.value}\n \u003C\u002Fli>\n ))\n : null}\n \u003C\u002Ful>\n \u003C\u002Fdiv>\n )}\n \u003C\u002FDownshift>,\n document.getElementById('root'),\n)\n```\n\nThere is also an [example without getRootProps][code-sandbox-no-get-root-props].\n\n> Warning: The example without `getRootProps` is not fully accessible with\n> screen readers as it's not possible to achieve the HTML structure suggested by\n> ARIA. We recommend following the example with `getRootProps`. Examples on how\n> to use `Downshift` component with and without `getRootProps` are on the\n> [docsite](https:\u002F\u002Fdownshift-js.com\u002F).\n\n`Downshift` is the only component exposed by this package. It doesn't render\nanything itself, it just calls the render function and renders that. [\"Use a\nrender prop!\"][use-a-render-prop]!\n`\u003CDownshift>{downshift => \u003Cdiv>\u002F* your JSX here! *\u002F\u003C\u002Fdiv>}\u003C\u002FDownshift>`.\n\n## Basic Props\n\nThis is the list of props that you should probably know about. There are some\n[advanced props](#advanced-props) below as well.\n\n### children\n\n> `function({})` | _required_\n\nThis is called with an object. Read more about the properties of this object in\nthe section \"[Children Function](#children-function)\".\n\n### itemToString\n\n> `function(item: any)` | defaults to: `item => (item ? String(item) : '')`\n\nIf your items are stored as, say, objects instead of strings, downshift still\nneeds a string representation for each one (e.g., to set `inputValue`).\n\n**Note:** This callback _must_ include a null check: it is invoked with `null`\nwhenever the user abandons input via `\u003CEsc>`.\n\n### onChange\n\n> `function(selectedItem: any, stateAndHelpers: object)` | optional, no useful\n> default\n\nCalled when the selected item changes, either by the user selecting an item or\nthe user clearing the selection. Called with the item that was selected or\n`null` and the new state of `downshift`. (see `onStateChange` for more info on\n`stateAndHelpers`).\n\n- `selectedItem`: The item that was just selected. `null` if the selection was\n cleared.\n- `stateAndHelpers`: This is the same thing your `children` function is called\n with (see [Children Function](#children-function))\n\n### stateReducer\n\n> `function(state: object, changes: object)` | optional\n\n**🚨 This is a really handy power feature 🚨**\n\nThis function will be called each time `downshift` sets its internal state (or\ncalls your `onStateChange` handler for control props). It allows you to modify\nthe state change that will take place which can give you fine grain control over\nhow the component interacts with user updates without having to use\n[Control Props](#control-props). It gives you the current state and the state\nthat will be set, and you return the state that you want to set.\n\n- `state`: The full current state of downshift.\n- `changes`: These are the properties that are about to change. This also has a\n `type` property which you can learn more about in the\n [`stateChangeTypes`](#statechangetypes) section.\n\n```jsx\nconst ui = (\n \u003CDownshift stateReducer={stateReducer}>{\u002F* your callback *\u002F}\u003C\u002FDownshift>\n)\n\nfunction stateReducer(state, changes) {\n \u002F\u002F this prevents the menu from being closed when the user\n \u002F\u002F selects an item with a keyboard or mouse\n switch (changes.type) {\n case Downshift.stateChangeTypes.keyDownEnter:\n case Downshift.stateChangeTypes.clickItem:\n return {\n ...changes,\n isOpen: state.isOpen,\n highlightedIndex: state.highlightedIndex,\n }\n default:\n return changes\n }\n}\n```\n\n> NOTE: This is only called when state actually changes. You should not attempt\n> to use this to handle events. If you wish to handle events, put your event\n> handlers directly on the elements (make sure to use the prop getters though!\n> For example: `\u003Cinput onBlur={handleBlur} \u002F>` should be\n> `\u003Cinput {...getInputProps({onBlur: handleBlur})} \u002F>`). Also, your reducer\n> function should be \"pure.\" This means it should do nothing other than return\n> the state changes you want to have happen.\n\n## Advanced Props\n\n### initialSelectedItem\n\n> `any` | defaults to `null`\n\nPass an item or an array of items that should be selected when downshift is\ninitialized.\n\n### initialInputValue\n\n> `string` | defaults to `''`\n\nThis is the initial input value when downshift is initialized.\n\n### initialHighlightedIndex\n\n> `number`\u002F`null` | defaults to `defaultHighlightedIndex`\n\nThis is the initial value to set the highlighted index to when downshift is\ninitialized.\n\n### initialIsOpen\n\n> `boolean` | defaults to `defaultIsOpen`\n\nThis is the initial `isOpen` value when downshift is initialized.\n\n### defaultHighlightedIndex\n\n> `number`\u002F`null` | defaults to `null`\n\nThis is the value to set the `highlightedIndex` to anytime downshift is reset,\nwhen the selection is cleared, when an item is selected or when the inputValue\nis changed.\n\n### defaultIsOpen\n\n> `boolean` | defaults to `false`\n\nThis is the value to set the `isOpen` to anytime downshift is reset, when the\nthe selection is cleared, or when an item is selected.\n\n### selectedItemChanged\n\n> `function(prevItem: any, item: any)` | defaults to:\n> `(prevItem, item) => (prevItem !== item)`\n\nUsed to determine if the new `selectedItem` has changed compared to the previous\n`selectedItem` and properly update Downshift's internal state.\n\n### getA11yStatusMessage\n\n> `function({\u002F* see below *\u002F})` | default messages provided in English\n\nThis function is passed as props to a `Status` component nested within and\nallows you to create your own assertive ARIA statuses.\n\nA default `getA11yStatusMessage` function is provided that will check\n`resultCount` and return \"No results are available.\" or if there are results ,\n\"`resultCount` results are available, use up and down arrow keys to navigate.\nPress Enter key to select.\"\n\nThe object you are passed to generate your status message has the following\nproperties:\n\n\u003C!-- This table was generated via http:\u002F\u002Fwww.tablesgenerator.com\u002Fmarkdown_tables -->\n\n| property | type | description |\n| --------------------- | --------------- | -------------------------------------------------------------------------------------------- |\n| `highlightedIndex` | `number`\u002F`null` | The currently highlighted index |\n| `highlightedItem` | `any` | The value of the highlighted item |\n| `inputValue` | `string` | The current input value |\n| `isOpen` | `boolean` | The `isOpen` state |\n| `itemToString` | `function(any)` | The `itemToString` function (see props) for getting the string value from one of the options |\n| `previousResultCount` | `number` | The total items showing in the dropdown the last time the status was updated |\n| `resultCount` | `number` | The total items showing in the dropdown |\n| `selectedItem` | `any` | The value of the currently selected item |\n\n### onSelect\n\n> `function(selectedItem: any, stateAndHelpers: object)` | optional, no useful\n> default\n\nCalled when the user selects an item, regardless of the previous selected item.\nCalled with the item that was selected and the new state of `downshift`. (see\n`onStateChange` for more info on `stateAndHelpers`).\n\n- `selectedItem`: The item that was just selected\n- `stateAndHelpers`: This is the same thing your `children` function is called\n with (see [Children Function](#children-function))\n\n### onStateChange\n\n> `function(changes: object, stateAndHelpers: object)` | optional, no useful\n> default\n\nThis function is called anytime the internal state changes. This can be useful\nif you're using downshift as a \"controlled\" component, where you manage some or\nall of the state (e.g., isOpen, selectedItem, highlightedIndex, etc) and then\npass it as props, rather than letting downshift control all its state itself.\nThe parameters both take the shape of internal state\n(`{highlightedIndex: number, inputValue: string, isOpen: boolean, selectedItem: any}`)\nbut differ slightly.\n\n- `changes`: These are the properties that actually have changed since the last\n state change. This also has a `type` property which you can learn more about\n in the [`stateChangeTypes`](#statechangetypes) section.\n- `stateAndHelpers`: This is the exact same thing your `children` function is\n called with (see [Children Function](#children-function))\n\n> Tip: This function will be called any time _any_ state is changed. The best\n> way to determine whether any particular state was changed, you can use\n> `changes.hasOwnProperty('propName')`.\n\n> NOTE: This is only called when state actually changes. You should not attempt\n> to use this to handle events. If you wish to handle events, put your event\n> handlers directly on the elements (make sure to use the prop getters though!\n> For example: `\u003Cinput onBlur={handleBlur} \u002F>` should be\n> `\u003Cinput {...getInputProps({onBlur: handleBlur})} \u002F>`).\n\n### onInputValueChange\n\n> `function(inputValue: string, stateAndHelpers: object)` | optional, no useful\n> default\n\nCalled whenever the input value changes. Useful to use instead or in combination\nof `onStateChange` when `inputValue` is a controlled prop to\n[avoid issues with cursor positions](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues\u002F217).\n\n- `inputValue`: The current value of the input\n- `stateAndHelpers`: This is the same thing your `children` function is called\n with (see [Children Function](#children-function))\n\n### itemCount\n\n> `number` | optional, defaults the number of times you call getItemProps\n\nThis is useful if you're using some kind of virtual listing component for\n\"windowing\" (like\n[`react-virtualized`](https:\u002F\u002Fgithub.com\u002Fbvaughn\u002Freact-virtualized)).\n\n### highlightedIndex\n\n> `number` | **control prop** (read more about this in\n> [the Control Props section](#control-props))\n\nThe index that should be highlighted\n\n### inputValue\n\n> `string` | **control prop** (read more about this in\n> [the Control Props section](#control-props))\n\nThe value the input should have\n\n### isOpen\n\n> `boolean` | **control prop** (read more about this in\n> [the Control Props section](#control-props))\n\nWhether the menu should be considered open or closed. Some aspects of the\ndownshift component respond differently based on this value (for example, if\n`isOpen` is true when the user hits \"Enter\" on the input field, then the item at\nthe `highlightedIndex` item is selected).\n\n### selectedItem\n\n> `any`\u002F`Array(any)` | **control prop** (read more about this in\n> [the Control Props section](#control-props))\n\nThe currently selected item.\n\n### id\n\n> `string` | defaults to a generated ID\n\nYou should not normally need to set this prop. It's only useful if you're server\nrendering items (which each have an `id` prop generated based on the `downshift`\n`id`). For more information see the `FAQ` below.\n\n### inputId\n\n> `string` | defaults to a generated ID\n\nUsed for `aria` attributes and the `id` prop of the element (`input`) you use\n[`getInputProps`](#getinputprops) with.\n\n### labelId\n\n> `string` | defaults to a generated ID\n\nUsed for `aria` attributes and the `id` prop of the element (`label`) you use\n[`getLabelProps`](#getlabelprops) with.\n\n### menuId\n\n> `string` | defaults to a generated ID\n\nUsed for `aria` attributes and the `id` prop of the element (`ul`) you use\n[`getMenuProps`](#getmenuprops) with.\n\n### getItemId\n\n> `function(index)` | defaults to a function that generates an ID based on the\n> index\n\nUsed for `aria` attributes and the `id` prop of the element (`li`) you use\n[`getInputProps`](#getinputprops) with.\n\n### environment\n\n> `window` | defaults to `window`\n\nThis prop is only useful if you're rendering downshift within a different\n`window` context from where your JavaScript is running; for example, an iframe\nor a shadow-root. If the given context is lacking `document` and\u002For\n`add|removeEventListener` on its prototype (as is the case for a shadow-root)\nthen you will need to pass in a custom object that is able to provide\n[access to these properties](https:\u002F\u002Fgist.github.com\u002FRendez\u002F1dd55882e9b850dd3990feefc9d6e177)\nfor downshift.\n\n### onOuterClick\n\n> `function(stateAndHelpers: object)` | optional\n\nA helper callback to help control internal state of downshift like `isOpen` as\nmentioned in [this issue](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues\u002F206).\nThe same behavior can be achieved using `onStateChange`, but this prop is\nprovided as a helper because it's a fairly common use-case if you're controlling\nthe `isOpen` state:\n\n```jsx\nconst ui = (\n \u003CDownshift\n isOpen={this.state.menuIsOpen}\n onOuterClick={() => this.setState({menuIsOpen: false})}\n >\n {\u002F* your callback *\u002F}\n \u003C\u002FDownshift>\n)\n```\n\nThis callback will only be called if `isOpen` is `true`.\n\n### scrollIntoView\n\n> `function(node: HTMLElement, menuNode: HTMLElement)` | defaults to internal\n> implementation\n\nThis allows you to customize how the scrolling works when the highlighted index\nchanges. It receives the node to be scrolled to and the root node (the root node\nyou render in downshift). Internally we use\n[`compute-scroll-into-view`](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fcompute-scroll-into-view)\nso if you use that package then you wont be adding any additional bytes to your\nbundle :)\n\n## stateChangeTypes\n\nThere are a few props that expose changes to state\n([`onStateChange`](#onstatechange) and [`stateReducer`](#statereducer)). For you\nto make the most of these APIs, it's important for you to understand why state\nis being changed. To accomplish this, there's a `type` property on the `changes`\nobject you get. This `type` corresponds to a `Downshift.stateChangeTypes`\nproperty.\n\nThe list of all possible values this `type` property can take is defined in\n[this file](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fblob\u002Fmaster\u002Fsrc\u002FstateChangeTypes.js)\nand is as follows:\n\n- `Downshift.stateChangeTypes.unknown`\n- `Downshift.stateChangeTypes.mouseUp`\n- `Downshift.stateChangeTypes.itemMouseEnter`\n- `Downshift.stateChangeTypes.keyDownArrowUp`\n- `Downshift.stateChangeTypes.keyDownArrowDown`\n- `Downshift.stateChangeTypes.keyDownEscape`\n- `Downshift.stateChangeTypes.keyDownEnter`\n- `Downshift.stateChangeTypes.keyDownHome`\n- `Downshift.stateChangeTypes.keyDownEnd`\n- `Downshift.stateChangeTypes.clickItem`\n- `Downshift.stateChangeTypes.blurInput`\n- `Downshift.stateChangeTypes.changeInput`\n- `Downshift.stateChangeTypes.keyDownSpaceButton`\n- `Downshift.stateChangeTypes.clickButton`\n- `Downshift.stateChangeTypes.blurButton`\n- `Downshift.stateChangeTypes.controlledPropUpdatedSelectedItem`\n- `Downshift.stateChangeTypes.touchEnd`\n\nSee [`stateReducer`](#statereducer) for a concrete example on how to use the\n`type` property.\n\n## Control Props\n\ndownshift manages its own state internally and calls your `onChange` and\n`onStateChange` handlers with any relevant changes. The state that downshift\nmanages includes: `isOpen`, `selectedItem`, `inputValue`, and\n`highlightedIndex`. Your Children function (read more below) can be used to\nmanipulate this state and can likely support many of your use cases.\n\nHowever, if more control is needed, you can pass any of these pieces of state as\na prop (as indicated above) and that state becomes controlled. As soon as\n`this.props[statePropKey] !== undefined`, internally, `downshift` will determine\nits state based on your prop's value rather than its own internal state. You\nwill be required to keep the state up to date (this is where `onStateChange`\ncomes in really handy), but you can also control the state from anywhere, be\nthat state from other components, `redux`, `react-router`, or anywhere else.\n\n> Note: This is very similar to how normal controlled components work elsewhere\n> in react (like `\u003Cinput \u002F>`). If you want to learn more about this concept, you\n> can learn about that from this the\n> [Advanced React Component Patterns course](#advanced-react-component-patterns-course)\n\n## Children Function\n\nThis is where you render whatever you want to based on the state of `downshift`.\nYou use it like so:\n\n```javascript\nconst ui = (\n \u003CDownshift>\n {downshift => (\n \u002F\u002F use downshift utilities and state here, like downshift.isOpen,\n \u002F\u002F downshift.getInputProps, etc.\n \u003Cdiv>{\u002F* more jsx here *\u002F}\u003C\u002Fdiv>\n )}\n \u003C\u002FDownshift>\n)\n```\n\nThe properties of this `downshift` object can be split into three categories as\nindicated below:\n\n### prop getters\n\n> See\n> [the blog post about prop getters](https:\u002F\u002Fkentcdodds.com\u002Fblog\u002Fhow-to-give-rendering-control-to-users-with-prop-getters)\n\n> NOTE: These prop-getters provide important `aria-` attributes which are very\n> important to your component being accessible. It's recommended that you\n> utilize these functions and apply the props they give you to your components.\n\nThese functions are used to apply props to the elements that you render. This\ngives you maximum flexibility to render what, when, and wherever you like. You\ncall these on the element in question (for example:\n`\u003Cinput {...getInputProps()}`)). It's advisable to pass all your props to that\nfunction rather than applying them on the element yourself to avoid your props\nbeing overridden (or overriding the props returned). For example:\n`getInputProps({onKeyUp(event) {console.log(event)}})`.\n\n\u003C!-- This table was generated via http:\u002F\u002Fwww.tablesgenerator.com\u002Fmarkdown_tables -->\n\n| property | type | description |\n| ---------------------- | ----------------- | ---------------------------------------------------------------------------------------------- |\n| `getToggleButtonProps` | `function({})` | returns the props you should apply to any menu toggle button element you render. |\n| `getInputProps` | `function({})` | returns the props you should apply to the `input` element that you render. |\n| `getItemProps` | `function({})` | returns the props you should apply to any menu item elements you render. |\n| `getLabelProps` | `function({})` | returns the props you should apply to the `label` element that you render. |\n| `getMenuProps` | `function({},{})` | returns the props you should apply to the `ul` element (or root of your menu) that you render. |\n| `getRootProps` | `function({},{})` | returns the props you should apply to the root element that you render. It can be optional. |\n\n#### `getRootProps`\n\n\u003Cdetails>\n\n\u003Csummary>\n If you cannot render a div as the root element, then read this\n\u003C\u002Fsummary>\n\nMost of the time, you can just render a `div` yourself and `Downshift` will\napply the props it needs to do its job (and you don't need to call this\nfunction). However, if you're rendering a composite component (custom component)\nas the root element, then you'll need to call `getRootProps` and apply that to\nyour root element (downshift will throw an error otherwise).\n\nThere are no required properties for this method.\n\nOptional properties:\n\n- `refKey`: if you're rendering a composite component, that component will need\n to accept a prop which it forwards to the root DOM element. Commonly, folks\n call this `innerRef`. So you'd call: `getRootProps({refKey: 'innerRef'})` and\n your composite component would forward like: `\u003Cdiv ref={props.innerRef} \u002F>`.\n It defaults to `ref`.\n\nIf you're rendering a composite component, `Downshift` checks that\n`getRootProps` is called and that `refKey` is a prop of the returned composite\ncomponent. This is done to catch common causes of errors but, in some cases, the\ncheck could fail even if the ref is correctly forwarded to the root DOM\ncomponent. In these cases, you can provide the object\n`{suppressRefError : true}` as the second argument to `getRootProps` to\ncompletely bypass the check.\\\n**Please use it with extreme care and only if you are absolutely sure that the\nref is correctly forwarded otherwise `Downshift` will unexpectedly fail.**\\\nSee [#235](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues\u002F235) for the\ndiscussion that lead to this.\n\n\u003C\u002Fdetails>\n\n#### `getInputProps`\n\nThis method should be applied to the `input` you render. It is recommended that\nyou pass all props as an object to this method which will compose together any\nof the event handlers you need to apply to the `input` while preserving the ones\nthat `downshift` needs to apply to make the `input` behave.\n\nThere are no required properties for this method.\n\nOptional properties:\n\n- `disabled`: If this is set to true, then no event handlers will be returned\n from `getInputProps` and a `disabled` prop will be returned (effectively\n disabling the input).\n\n- `aria-label`: By default the menu will add an `aria-labelledby` that refers to\n the `\u003Clabel>` rendered with `getLabelProps`. However, if you provide\n `aria-label` to give a more specific label that describes the options\n available, then `aria-labelledby` will not be provided and screen readers can\n use your `aria-label` instead.\n\n#### `getLabelProps`\n\nThis method should be applied to the `label` you render. It is useful for\nensuring that the `for` attribute on the `\u003Clabel>` (`htmlFor` as a react prop)\nis the same as the `id` that appears on the `input`. If no `htmlFor` is provided\n(the normal case) then an ID will be generated and used for the `input` and the\n`label` `for` attribute.\n\nThere are no required properties for this method.\n\n> Note: For accessibility purposes, calling this method is highly recommended.\n\n#### `getMenuProps`\n\nThis method should be applied to the element which contains your list of items.\nTypically, this will be a `\u003Cdiv>` or a `\u003Cul>` that surrounds a `map` expression.\nThis handles the proper ARIA roles and attributes.\n\nOptional properties:\n\n- `refKey`: if you're rendering a composite component, that component will need\n to accept a prop which it forwards to the root DOM element. Commonly, folks\n call this `innerRef`. So you'd call: `getMenuProps({refKey: 'innerRef'})` and\n your composite component would forward like: `\u003Cul ref={props.innerRef} \u002F>`.\n However, if you are just rendering a primitive component like `\u003Cdiv>`, there\n is no need to specify this property. It defaults to `ref`.\n\n Please keep in mind that menus, for accessibility purposes, should always be\n rendered, regardless of whether you hide it or not. Otherwise, `getMenuProps`\n may throw error if you unmount and remount the menu.\n\n- `aria-label`: By default the menu will add an `aria-labelledby` that refers to\n the `\u003Clabel>` rendered with `getLabelProps`. However, if you provide\n `aria-label` to give a more specific label that describes the options\n available, then `aria-labelledby` will not be provided and screen readers can\n use your `aria-label` instead.\n\nIn some cases, you might want to completely bypass the `refKey` check. Then you\ncan provide the object `{suppressRefError : true}` as the second argument to\n`getMenuProps`. **Please use it with extreme care and only if you are absolutely\nsure that the ref is correctly forwarded otherwise `Downshift` will unexpectedly\nfail.**\n\n```jsx\n\u003Cul {...getMenuProps()}>\n {!isOpen\n ? null\n : items.map((item, index) => (\n \u003Cli {...getItemProps({item, index, key: item.id})}>{item.name}\u003C\u002Fli>\n ))}\n\u003C\u002Ful>\n```\n\n> Note that for accessibility reasons it's best if you always render this\n> element whether or not downshift is in an `isOpen` state.\n\n#### `getItemProps`\n\nThe props returned from calling this function should be applied to any menu\nitems you render.\n\n**This is an impure function**, so it should only be called when you will\nactually be applying the props to an item.\n\n\u003Cdetails>\n\n\u003Csummary>What do you mean by impure function?\u003C\u002Fsummary>\n\nBasically just don't do this:\n\n```jsx\nitems.map(item => {\n const props = getItemProps({item}) \u002F\u002F we're calling it here\n if (!shouldRenderItem(item)) {\n return null \u002F\u002F but we're not using props, and downshift thinks we are...\n }\n return \u003Cdiv {...props} \u002F>\n})\n```\n\nInstead, you could do this:\n\n```jsx\nitems.filter(shouldRenderItem).map(item => \u003Cdiv {...getItemProps({item})} \u002F>)\n```\n\n\u003C\u002Fdetails>\n\nRequired properties:\n\n- `item`: this is the item data that will be selected when the user selects a\n particular item.\n\nOptional properties:\n\n- `index`: This is how `downshift` keeps track of your item when updating the\n `highlightedIndex` as the user keys around. By default, `downshift` will\n assume the `index` is the order in which you're calling `getItemProps`. This\n is often good enough, but if you find odd behavior, try setting this\n explicitly. It's probably best to be explicit about `index` when using a\n windowing library like `react-virtualized`.\n- `disabled`: If this is set to `true`, then all of the downshift item event\n handlers will be omitted. Items will not be highlighted when hovered, and\n items will not be selected when clicked.\n\n#### `getToggleButtonProps`\n\nCall this and apply the returned props to a `button`. It allows you to toggle\nthe `Menu` component. You can definitely build something like this yourself (all\nof the available APIs are exposed to you), but this is nice because it will also\napply all of the proper ARIA attributes.\n\nOptional properties:\n\n- `disabled`: If this is set to `true`, then all of the downshift button event\n handlers will be omitted (it wont toggle the menu when clicked).\n- `aria-label`: The `aria-label` prop is in English. You should probably\n override this yourself so you can provide translations:\n\n```jsx\nconst myButton = (\n \u003Cbutton\n {...getToggleButtonProps({\n 'aria-label': translateWithId(isOpen ? 'close.menu' : 'open.menu'),\n })}\n \u002F>\n)\n```\n\n### actions\n\nThese are functions you can call to change the state of the downshift component.\n\n\u003C!-- This table was generated via http:\u002F\u002Fwww.tablesgenerator.com\u002Fmarkdown_tables -->\n\n| property | type | description |\n| ----------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `clearSelection` | `function(cb: Function)` | clears the selection |\n| `clearItems` | `function()` | Clears downshift's record of all the items. Only really useful if you render your items asynchronously within downshift. See [#186](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues\u002F186) |\n| `closeMenu` | `function(cb: Function)` | closes the menu |\n| `openMenu` | `function(cb: Function)` | opens the menu |\n| `selectHighlightedItem` | `function(otherStateToSet: object, cb: Function)` | selects the item that is currently highlighted |\n| `selectItem` | `function(item: any, otherStateToSet: object, cb: Function)` | selects the given item |\n| `selectItemAtIndex` | `function(index: number, otherStateToSet: object, cb: Function)` | selects the item at the given index |\n| `setHighlightedIndex` | `function(index: number, otherStateToSet: object, cb: Function)` | call to set a new highlighted index |\n| `toggleMenu` | `function(otherStateToSet: object, cb: Function)` | toggle the menu open state |\n| `reset` | `function(otherStateToSet: object, cb: Function)` | this resets downshift's state to a reasonable default |\n| `setItemCount` | `function(count: number)` | this sets the `itemCount`. Handy in situations where you're using windowing and the items are loaded asynchronously from within downshift (so you can't use the `itemCount` prop. |\n| `unsetItemCount` | `function()` | this unsets the `itemCount` which means the item count will be calculated instead by the `itemCount` prop or based on how many times you call `getItemProps`. |\n| `setState` | `function(stateToSet: object, cb: Function)` | This is a general `setState` function. It uses downshift's `internalSetState` function which works with control props and calls your `onSelect`, `onChange`, etc. (Note, you can specify a `type` which you can reference in some other APIs like the `stateReducer`). |\n\n> `otherStateToSet` refers to an object to set other internal state. It is\n> recommended to avoid abusing this, but is available if you need it.\n\n### state\n\nThese are values that represent the current state of the downshift component.\n\n\u003C!-- This table was generated via http:\u002F\u002Fwww.tablesgenerator.com\u002Fmarkdown_tables -->\n\n| property | type | description |\n| ------------------ | ----------------- | ---------------------------------------------- |\n| `highlightedIndex` | `number` \u002F `null` | the currently highlighted item |\n| `inputValue` | `string` \u002F `null` | the current value of the `getInputProps` input |\n| `isOpen` | `boolean` | the menu open state |\n| `selectedItem` | `any` | the currently selected item input |\n\n### props\n\nAs a convenience, the `id` and `itemToString` props which you pass to\n`\u003CDownshift \u002F>` are available here as well.\n\n## Event Handlers\n\nDownshift has a few events for which it provides implicit handlers. Several of\nthese handlers call `event.preventDefault()`. Their additional functionality is\ndescribed below.\n\n### default handlers\n\n- `ArrowDown`: if menu is closed, opens it and moves the highlighted index to\n `defaultHighlightedIndex + 1`, if `defaultHighlightedIndex` is provided, or to\n the top-most item, if not. If menu is open, it moves the highlighted index\n down by 1. If the shift key is held when this event fires, the highlighted\n index will jump down 5 indices instead of 1. NOTE: if the current highlighted\n index is within the bottom 5 indices, the top-most index will be highlighted.)\n\n- `ArrowUp`: if menu is closed, opens it and moves the highlighted index to\n `defaultHighlightedIndex - 1`, if `defaultHighlightedIndex` is provided, or to\n the bottom-most item, if not. If menu is open, moves the highlighted index up\n by 1. If the shift key is held when this event fires, the highlighted index\n will jump up 5 indices instead of 1. NOTE: if the current highlighted index is\n within the top 5 indices, the bottom-most index will be highlighted.)\n\n- `Home`: if menu is closed, it will not add any other behavior. If menu is\n open, the top-most index will get highlighted.\n\n- `End`: if menu is closed, it will not add any other behavior. If menu is open,\n the bottom-most index will get highlighted.\n\n- `Enter`: if the menu is open, selects the currently highlighted item. If the\n menu is open, the usual 'Enter' event is prevented by Downshift's default\n implicit enter handler; so, for example, a form submission event will not work\n as one might expect (though if the menu is closed the form submission will\n work normally). See below for customizing the handlers.\n\n- `Escape`: will clear downshift's state. This means that `highlightedIndex`\n will be set to the `defaultHighlightedIndex` and the `isOpen` state will be\n set to the `defaultIsOpen`. If `isOpen` is already false, the `inputValue`\n will be set to an empty string and `selectedItem` will be set to `null`\n\n### customizing handlers\n\nYou can provide your own event handlers to Downshift which will be called before\nthe default handlers:\n\n```javascript\nconst ui = (\n \u003CDownshift>\n {({getInputProps}) => (\n \u003Cinput\n {...getInputProps({\n onKeyDown: event => {\n \u002F\u002F your handler code\n },\n })}\n \u002F>\n )}\n \u003C\u002FDownshift>\n)\n```\n\nIf you would like to prevent the default handler behavior in some cases, you can\nset the event's `preventDownshiftDefault` property to `true`:\n\n```javascript\nconst ui = (\n \u003CDownshift>\n {({getInputProps}) => (\n \u003Cinput\n {...getInputProps({\n onKeyDown: event => {\n if (event.key === 'Enter') {\n \u002F\u002F Prevent Downshift's default 'Enter' behavior.\n event.nativeEvent.preventDownshiftDefault = true\n\n \u002F\u002F your handler code\n }\n },\n })}\n \u002F>\n )}\n \u003C\u002FDownshift>\n)\n```\n\nIf you would like to completely override Downshift's behavior for a handler, in\nfavor of your own, you can bypass prop getters:\n\n```javascript\nconst ui = (\n \u003CDownshift>\n {({getInputProps}) => (\n \u003Cinput\n {...getInputProps()}\n onKeyDown={event => {\n \u002F\u002F your handler code\n }}\n \u002F>\n )}\n \u003C\u002FDownshift>\n)\n```\n\n## Utilities\n\n### resetIdCounter\n\nAllows reseting the internal id counter which is used to generate unique ids for\nDownshift component.\n\n**This is unnecessary if you are using React 18 or newer**\n\nYou should never need to use this in the browser. Only if you are running an\nuniversal React app that is rendered on the server you should call\n[resetIdCounter](#resetidcounter) before every render so that the ids that get\ngenerated on the server match the ids generated in the browser.\n\n```javascript\nimport {resetIdCounter} from 'downshift';\n\nresetIdCounter()\nReactDOMServer.renderToString(...);\n```\n\n## React Native\n\nSince Downshift renders it's UI using render props, Downshift supports rendering\non React Native with ease. Use components like `\u003CView>`, `\u003CText>`,\n`\u003CTouchableOpacity>` and others inside of your render method to generate awesome\nautocomplete, dropdown, or selection components.\n\n### Gotchas\n\n- Your root view will need to either pass a ref to `getRootProps` or call\n `getRootProps` with `{ suppressRefError: true }`. This ref is used to catch a\n common set of errors around composite components.\n [Learn more in `getRootProps`](#getrootprops).\n- When using a `\u003CFlatList>` or `\u003CScrollView>`, be sure to supply the\n [`keyboardShouldPersistTaps`](https:\u002F\u002Ffacebook.github.io\u002Freact-native\u002Fdocs\u002Fscrollview.html#keyboardshouldpersisttaps)\n prop to ensure that your text input stays focus, while allowing for taps on\n the touchables rendered for your items.\n\n## Advanced React Component Patterns course\n\n[Kent C. Dodds](https:\u002F\u002Ftwitter.com\u002Fkentcdodds) has created learning material\nbased on the patterns implemented in this component. You can find it on various\nplatforms:\n\n1. [egghead.io](https:\u002F\u002Fegghead.io\u002Fcourses\u002Fadvanced-react-component-patterns)\n2. [Frontend Masters](https:\u002F\u002Ffrontendmasters.com\u002Fcourses\u002Fadvanced-react-patterns\u002F)\n3. YouTube (for free!):\n [Part 1](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=SuzutbwjUp8&list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf)\n and\n [Part 2](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=ubXtOROjILU&list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf)\n\n## Examples\n\n> 🚨 We're in the process of moving all examples to the\n> [downshift-examples](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift-examples) repo\n> (which you can open, interact with, and contribute back to live on\n> [codesandbox](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Findex.js&moduleview=1))\n\n> 🚨 We're also in the process of updating our examples from the\n> [downshift-docs](https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift-docs) repo which is\n> actually used to create our docsite at [downshift-js.com][docsite]). Make sure\n> to check it out for the most relevant Downshift examples or try out the new\n> hooks that aim to replace Downshift.\n\n**Ordered Examples:**\n\nIf you're just learning downshift, review these in order:\n\n0. [basic automplete with getRootProps](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fordered-examples%2F00-get-root-props-example.js%3A11%2C21&moduleview=1) -\n the same as example #1 but using the correct HTML structure as suggested by\n ARIA-WCAG.\n1. [basic autocomplete](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fordered-examples%2F01-basic-autocomplete.js&moduleview=1) -\n very bare bones, not styled at all. Good place to start.\n2. [styled autocomplete](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fordered-examples%2F02-complete-autocomplete.js&moduleview=1) -\n more complete autocomplete solution using emotion for styling and\n match-sorter for filtering the items.\n3. [typeahead](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fordered-examples%2F03-typeahead.js&moduleview=1) -\n Shows how to control the `selectedItem` so the selected item can be one of\n your items or whatever the user types.\n4. [multi-select](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fordered-examples%2F04-multi-select.js&moduleview=1) -\n Shows how to create a MultiDownshift component that allows for an array of\n selectedItems for multiple selection using a state reducer\n\n**Other Examples:**\n\nCheck out these examples of more advanced use\u002Fedge cases:\n\n- [dropdown with select by key](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fother-examples%2Fdropdown-select-by-key%2FCustomDropdown%2Findex.js&moduleview=1) -\n An example of using the render prop pattern to utilize a reusable component to\n provide the downshift dropdown component with the functionality of being able\n to highlight a selection item that starts with the key pressed.\n- [using actions](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fother-examples%2Fusing-actions.js&moduleview=1) -\n An example of using one of downshift's actions as an event handler.\n- [gmail's composition recipients field](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fother-examples%2Fgmail%2Findex.js&moduleview=1) -\n An example of a highly complex autocomplete component featuring asynchronously\n loading items, multiple selection, and windowing (with react-virtualized)\n- [Downshift HOC and Compound Components](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Fdownshift%2Fother-examples%2Fhoc%2Findex.js&moduleview=1) -\n An example of how to implementat compound components with\n `React.createContext` and a downshift higher order component. This is\n generally not recommended because the render prop API exported by downshift is\n generally good enough for everyone, but there's nothing technically wrong with\n doing something like this.\n\n**Old Examples exist on [codesandbox.io][examples]:**\n\n_🚨 This is a great contribution opportunity!_ These are examples that have not\nyet been migrated to\n[downshift-examples](https:\u002F\u002Fcodesandbox.io\u002Fp\u002Fsandbox\u002Fgithub\u002Fkentcdodds\u002Fdownshift-examples?file=%2Fsrc%2Findex.js&moduleview=1).\nYou're more than welcome to make PRs to the examples repository to move these\nexamples over there.\n[Watch this to learn how to contribute completely in the browser](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=3PAQbhdkTtI&index=2&t=21s&list=PLV5CVI1eNcJgCrPH_e6d57KRUTiDZgs0u)\n\n- [Integration with Apollo](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fm5zrvqj85p)\n- [Integration with Redux](https:\u002F\u002Fcodesandbox.io\u002Fs\u002F3ywmnyr0zq)\n- [Integration with `react-instantsearch`](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fkvn0lpp83)\n from Algolia\n- [Material-UI (1.0.0-beta.4) Combobox Using Downshift](https:\u002F\u002Fcodesandbox.io\u002Fs\u002FQMGq4kAY)\n- [Material-UI (1.0.0-beta.33) Multiple select with autocomplete](https:\u002F\u002Fcodesandbox.io\u002Fs\u002F7k3674z09q)\n- [Integration with `GenieJS`](https:\u002F\u002Fcodesandbox.io\u002Fs\u002FjRLKrxwgl)\n ([learn more about `genie` here](https:\u002F\u002Fgithub.com\u002Fkentcdodds\u002Fgenie))\n- [Handling and displaying errors](https:\u002F\u002Fcodesandbox.io\u002Fs\u002FzKE37vorr)\n- [Integration with React Router](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fww9lwloy8w)\n- [Windowing with `react-tiny-virtual-list`](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fv670kq95l)\n- [Section\u002Foption group example](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fzx1kj58npl)\n- [Integration with `fuzzaldrin-plus` (Fuzzy matching)](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fpyq3v4o3j)\n- [Dropdown\u002Fselect implementation with Bootstrap](https:\u002F\u002Fcodesandbox.io\u002Fs\u002F53y8jvpj0k)\n- [Multiple editable tag selection](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fo4yp9vmm8z)\n- [Downshift implemented as compound components and a Higher Order Component](https:\u002F\u002Fcodesandbox.io\u002Fs\u002F017n1jqo00)\n (exposes a `withDownshift` higher order component which you can use to get at\n the state, actions, prop getters in a rendered downshift tree).\n- [Downshift Spectre.css example](https:\u002F\u002Fcodesandbox.io\u002Fs\u002FM89KQOBRB)\n- [Integration with `redux-form`](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fk594964z13)\n- [Integration with `react-final-form`](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fqzm43nn2mj)\n- [Provider Pattern](https:\u002F\u002Fcodesandbox.io\u002Fs\u002Fmywzk3133p) - how to avoid\n prop-drilling if you like to break up your render method into more components\n- [React Native example](https:\u002F\u002Fsnack.expo.io\u002FSkE0LxXqM)\n- [React VR example](https:\u002F\u002Fgithub.com\u002Finfiniteluke\u002Fbassdrop)\n- [Multiple checkbox selection](https:\u002F\u002Fcodesandbox.io\u002Fs\u002F5z711pmr3l)\n\n## FAQ\n\n\u003Cdetails>\n\n\u003Csummary>\n How do I avoid the checksum error when server rendering (SSR)?\n\u003C\u002Fsummary>\n\nThe checksum error you're seeing is most likely due to the automatically\ngenerated `id` and\u002For `htmlFor` prop you get from `getInputProps` and\n`getLabelProps` (respectively). It could also be from the automatically\ngenerated `id` prop you get from `getItemProps` (though this is not likely as\nyou're probably not rendering any items when rendering a downshift component on\nthe server).\n\nTo avoid these problems, simply call [resetIdCounter](#resetidcounter) before\n`ReactDOM.renderToString`.\n\nAlternatively you could provide your own ids via the id props where you render\n`\u003CDownshift \u002F>`:\n\n```javascript\nconst ui = (\n \u003CDownshift\n id=\"autocomplete\"\n labelId=\"autocomplete-label\"\n inputId=\"autocomplete-input\"\n menuId=\"autocomplete-menu\"\n >\n {({getInputProps, getLabelProps}) => \u003Cdiv>{\u002F* your UI *\u002F}\u003C\u002Fdiv>}\n \u003C\u002FDownshift>\n)\n```\n\n\u003C\u002Fdetails>\n\n## Inspiration\n\nI was heavily inspired by [Ryan Florence][ryan]. Watch his (free) lesson about\n[\"Compound Components\"][compound-components-lecture]. Initially downshift was a\ngroup of compound components using context to communicate. But then [Jared\nForsyth][jared] suggested I expose functions (the prop getters) to get props to\napply to the elements rendered. That bit of inspiration made a big impact on the\nflexibility and simplicity of this API.\n\nI also took a few ideas from the code in\n[`react-autocomplete`][react-autocomplete] and [jQuery UI's\nAutocomplete][jquery-complete].\n\nYou can watch me build the first iteration of `downshift` on YouTube:\n\n- [Part 1](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=2kzD1IjDy5s&list=PLV5CVI1eNcJh5CTgArGVwANebCrAh2OUE&index=11)\n- [Part 2](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=w1Z7Jvj08_s&list=PLV5CVI1eNcJh5CTgArGVwANebCrAh2OUE&index=10)\n\nYou'll find more recordings of me working on `downshift` on [my livestream\nYouTube playlist][yt-playlist].\n\n## Other Solutions\n\nYou can implement these other solutions using `downshift`, but if you'd prefer\nto use these out of the box solutions, then that's fine too:\n\n- [`react-select`](https:\u002F\u002Fgithub.com\u002FJedWatson\u002Freact-select)\n- [`react-autosuggest`](https:\u002F\u002Fgithub.com\u002Fmoroshko\u002Freact-autosuggest)\n\n## Bindings for ReasonML\n\nIf you're developing some React in ReasonML, check out the\n[`Downshift` bindings](https:\u002F\u002Fgithub.com\u002Freasonml-community\u002Fbs-downshift) for\nthat.\n\n## Contributors\n\nThanks goes to these people ([emoji key][emojis]):\n\n\u003C!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->\n\u003C!-- prettier-ignore-start -->\n\u003C!-- markdownlint-disable -->\n\u003Ctable>\n \u003Ctbody>\n \u003Ctr>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fkentcdodds.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1500684?v=3?s=100\" width=\"100px;\" alt=\"Kent C. Dodds\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Kent C. Dodds\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=kentcdodds\" title=\"Code\">💻\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=kentcdodds\" title=\"Documentation\">📖\u003C\u002Fa> \u003Ca href=\"#infra-kentcdodds\" title=\"Infrastructure (Hosting, Build-Tools, etc)\">🚇\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=kentcdodds\" title=\"Tests\">⚠️\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fpulls?q=is%3Apr+reviewed-by%3Akentcdodds\" title=\"Reviewed Pull Requests\">👀\u003C\u002Fa> \u003Ca href=\"#blog-kentcdodds\" title=\"Blogposts\">📝\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Akentcdodds\" title=\"Bug reports\">🐛\u003C\u002Fa> \u003Ca href=\"#example-kentcdodds\" title=\"Examples\">💡\u003C\u002Fa> \u003Ca href=\"#ideas-kentcdodds\" title=\"Ideas, Planning, & Feedback\">🤔\u003C\u002Fa> \u003Ca href=\"#talk-kentcdodds\" title=\"Talks\">📢\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Ftwitter.com\u002Fryanflorence\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F100200?v=4?s=100\" width=\"100px;\" alt=\"Ryan Florence\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Ryan Florence\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#ideas-ryanflorence\" title=\"Ideas, Planning, & Feedback\">🤔\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fjaredforsyth.com\">\u003Cimg src=\"https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F112170?v=4?s=100\" width=\"100px;\" alt=\"Jared Forsyth\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Jared Forsyth\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#ideas-jaredly\" title=\"Ideas, Planning, & Feedback\">🤔\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=jaredly\" title=\"Documentation\">📖\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjtmthf\">\u003Cimg src=\"https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F8162598?v=4?s=100\" width=\"100px;\" alt=\"Jack Moore\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Jack Moore\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-jtmthf\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fsouporserious.com\u002F\">\u003Cimg src=\"https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F2762082?v=4?s=100\" width=\"100px;\" alt=\"Travis Arnold\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Travis Arnold\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=souporserious\" title=\"Code\">💻\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=souporserious\" title=\"Documentation\">📖\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fmarcysutton.com\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F1045233?v=4?s=100\" width=\"100px;\" alt=\"Marcy Sutton\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Marcy Sutton\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Amarcysutton\" title=\"Bug reports\">🐛\u003C\u002Fa> \u003Ca href=\"#ideas-marcysutton\" title=\"Ideas, Planning, & Feedback\">🤔\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fwww.jeremygayed.com\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F244704?v=4?s=100\" width=\"100px;\" alt=\"Jeremy Gayed\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Jeremy Gayed\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-tizmagik\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003C\u002Ftr>\n \u003Ctr>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fharoen.me\">\u003Cimg src=\"https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F6270048?v=4?s=100\" width=\"100px;\" alt=\"Haroen Viaene\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Haroen Viaene\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-Haroenv\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frezof\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F15073300?v=4?s=100\" width=\"100px;\" alt=\"monssef\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>monssef\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-rezof\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Ffezvrasta.github.io\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F5382443?v=4?s=100\" width=\"100px;\" alt=\"Federico Zivolo\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Federico Zivolo\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=FezVrasta\" title=\"Documentation\">📖\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fdivyendusingh.com\">\u003Cimg src=\"https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F746482?v=4?s=100\" width=\"100px;\" alt=\"Divyendu Singh\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Divyendu Singh\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-divyenduz\" title=\"Examples\">💡\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=divyenduz\" title=\"Code\">💻\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=divyenduz\" title=\"Documentation\">📖\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=divyenduz\" title=\"Tests\">⚠️\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsalmanmanekia\">\u003Cimg src=\"https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F841955?v=4?s=100\" width=\"100px;\" alt=\"Muhammad Salman\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Muhammad Salman\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=salmanmanekia\" title=\"Code\">💻\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fpsicotropidev\">\u003Cimg src=\"https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F10820159?v=4?s=100\" width=\"100px;\" alt=\"João Alberto\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>João Alberto\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=psicotropicos\" title=\"Code\">💻\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fbernard-lin\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F16327281?v=4?s=100\" width=\"100px;\" alt=\"Bernard Lin\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Bernard Lin\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=bernard-lin\" title=\"Code\">💻\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=bernard-lin\" title=\"Documentation\">📖\u003C\u002Fa>\u003C\u002Ftd>\n \u003C\u002Ftr>\n \u003Ctr>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgeoffdavis.info\">\u003Cimg src=\"https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F7330124?v=4?s=100\" width=\"100px;\" alt=\"Geoff Davis\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Geoff Davis\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#example-geoffdavis92\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Freznord\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F3415488?v=4?s=100\" width=\"100px;\" alt=\"Anup\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Anup\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=reznord\" title=\"Documentation\">📖\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fferdinandsalis.com\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F340520?v=4?s=100\" width=\"100px;\" alt=\"Ferdinand Salis\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Ferdinand Salis\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Aferdinandsalis\" title=\"Bug reports\">🐛\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=ferdinandsalis\" title=\"Code\">💻\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftkh44\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F662750?v=4?s=100\" width=\"100px;\" alt=\"Kye Hohenberger\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Kye Hohenberger\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Atkh44\" title=\"Bug reports\">🐛\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjgoux\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F1443499?v=4?s=100\" width=\"100px;\" alt=\"Julien Goux\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Julien Goux\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Ajgoux\" title=\"Bug reports\">🐛\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=jgoux\" title=\"Code\">💻\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=jgoux\" title=\"Tests\">⚠️\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjseminck\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F9586897?v=4?s=100\" width=\"100px;\" alt=\"Joachim Seminck\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Joachim Seminck\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=jseminck\" title=\"Code\">💻\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fjesseharlin.net\u002F\">\u003Cimg src=\"https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F954596?v=4?s=100\" width=\"100px;\" alt=\"Jesse Harlin\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Jesse Harlin\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fissues?q=author%3Athe-simian\" title=\"Bug reports\">🐛\u003C\u002Fa> \u003Ca href=\"#example-the-simian\" title=\"Examples\">💡\u003C\u002Fa>\u003C\u002Ftd>\n \u003C\u002Ftr>\n \u003Ctr>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpbomb\">\u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F1402095?v=4?s=100\" width=\"100px;\" alt=\"Matt Parrish\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>Matt Parrish\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"#tool-pbomb\" title=\"Tools\">🔧\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fpulls?q=is%3Apr+reviewed-by%3Apbomb\" title=\"Reviewed Pull Requests\">👀\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Fthom.kr\">\u003Cimg src=\"https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F11661846?v=4?s=100\" width=\"100px;\" alt=\"thom\"\u002F>\u003Cbr \u002F>\u003Csub>\u003Cb>thom\u003C\u002Fb>\u003C\u002Fsub>\u003C\u002Fa>\u003Cbr \u002F>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdownshift-js\u002Fdownshift\u002Fcommits?author=thomhos\" title=\"Code\">💻\u003C\u002Fa>\u003C\u002Ftd>\n \u003Ctd align=\"center\" valign=\"top\" width=\"14.28%\">\u003Ca href=\"http:\u002F\u002Ftwitter.com\u002Ftranvu\">\u003Cimg src=\"https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F1088312?v=4?s=100\" wi","downshift 是一个用于构建简单、灵活且符合 WAI-ARIA 标准的 React 自动完成、组合框或下拉选择组件的基础库。它提供了包括 useSelect、useCombobox 和 useTagGroup 在内的多个 React Hooks，这些 Hooks 能够为自定义组件提供所需的状态逻辑，确保其功能性和可访问性。此外，还包含一个名为 Downshift 的组件，通过 render prop 的形式提供逻辑支持。downshift 适用于需要在应用中添加自动完成功能、组合框或下拉菜单，并且重视无障碍设计的场景。项目采用 MIT 许可证，拥有广泛的社区支持和活跃的开发贡献者。",2,"2026-06-11 02:54:27","top_language"]