react-autosuggest vs react-select vs selectize
React Component Libraries for Select Inputs
react-autosuggestreact-selectselectizeSimilar Packages:

React Component Libraries for Select Inputs

These libraries provide advanced solutions for creating user-friendly select input components in React applications. They enhance the user experience by offering features like autocomplete suggestions, multi-select capabilities, and customizable styling. Each library has its unique strengths, making them suitable for different use cases in web development. Understanding their functionalities and design principles can help developers choose the right tool for their specific needs.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
react-autosuggest05,954-2605 years agoMIT
react-select028,060726 kB4858 months agoMIT
selectize013,059-468 years agoApache-2.0

Feature Comparison: react-autosuggest vs react-select vs selectize

Customization

  • react-autosuggest:

    react-autosuggest allows for basic customization of the suggestion list and input field, but it is primarily focused on providing a functional autocomplete experience. Developers can style the input and suggestion list through CSS, but the core functionality is more rigid compared to others.

  • react-select:

    react-select offers extensive customization options, allowing developers to modify nearly every aspect of the component, including styles, components, and behavior. It supports custom rendering for options and allows for complete control over the dropdown's appearance and functionality.

  • selectize:

    selectize provides a good level of customization, allowing developers to style the input and dropdown using CSS. It also supports custom item rendering and can be extended with plugins, making it versatile for different use cases.

Performance

  • react-autosuggest:

    react-autosuggest is optimized for performance with efficient rendering of suggestions based on user input. It minimizes re-renders by using controlled components and is designed to handle large datasets smoothly, making it suitable for applications with extensive suggestion lists.

  • react-select:

    react-select can handle large datasets efficiently with features like virtualized rendering and asynchronous loading of options. However, performance may vary based on the complexity of the custom components used, so developers should be mindful of performance implications when customizing extensively.

  • selectize:

    selectize is generally performant but can experience slowdowns with very large datasets due to its jQuery foundation. It is best suited for smaller to medium datasets unless optimized with remote data fetching.

User Experience

  • react-autosuggest:

    react-autosuggest provides a clean and intuitive user experience focused on autocomplete functionality. It enhances usability by displaying suggestions as the user types, making it easy to find options quickly without overwhelming the user with choices.

  • react-select:

    react-select excels in user experience with features like multi-select, search functionality, and the ability to group options. Its flexible design allows for a more interactive and engaging selection process, catering to complex user needs.

  • selectize:

    selectize offers a user-friendly interface with tagging capabilities and a straightforward selection process. It is particularly effective for scenarios where users need to create custom tags or select multiple items, enhancing the overall interaction.

Integration

  • react-autosuggest:

    react-autosuggest integrates seamlessly with React applications, leveraging React's component lifecycle for efficient updates. It is easy to implement and requires minimal setup, making it a great choice for projects focused on simplicity and speed.

  • react-select:

    react-select is built specifically for React, ensuring smooth integration with React's state management and lifecycle methods. It is well-documented and widely used, providing a robust solution for any React application needing select inputs.

  • selectize:

    selectize is a jQuery plugin, which may require additional effort to integrate into React applications. While it can be used within React, it may not leverage React's full capabilities, potentially leading to challenges in managing state and updates.

Community and Support

  • react-autosuggest:

    react-autosuggest has a smaller community compared to the others, but it is still actively maintained and supported. Documentation is clear, making it easier for developers to get started and find solutions to common issues.

  • react-select:

    react-select has a large and active community, providing extensive documentation, examples, and community support. It is widely adopted, which means developers can find numerous resources and third-party extensions to enhance its functionality.

  • selectize:

    selectize has a moderate community presence, but it is not as actively maintained as the other two. While it has decent documentation, developers may find fewer resources and community support compared to react-select.

How to Choose: react-autosuggest vs react-select vs selectize

  • react-autosuggest:

    Choose react-autosuggest if you need an autocomplete input that provides suggestions based on user input, making it ideal for search fields or any scenario where users benefit from predictive text. It is lightweight and focuses on providing a seamless suggestion experience.

  • react-select:

    Choose react-select if you require a highly customizable select input with support for multi-select, async options, and advanced features like grouping and searching. It is suitable for complex forms where users need to select one or multiple options from a large dataset.

  • selectize:

    Choose selectize if you want a jQuery-based solution that offers a rich feature set, including tagging, remote data sets, and a user-friendly interface. It is beneficial for projects that already use jQuery and require a more traditional approach to select inputs.

README for react-autosuggest

Build Status Contributors Coverage Status

npm Downloads npm Version gzip size

React Autosuggest

Project Status

Looking for maintainers!

Unfortunately, I don't have the time to maintain this project anymore. If you are interested to help, please reach out to me on Twitter @moroshko.

Demo

Check out the Homepage and the Codepen examples.

Features

Installation

yarn add react-autosuggest

or

npm install react-autosuggest --save

You can also use the standalone UMD build:

<script src="https://unpkg.com/react-autosuggest/dist/standalone/autosuggest.js"></script>

Basic Usage

import React from 'react';
import Autosuggest from 'react-autosuggest';

// Imagine you have a list of languages that you'd like to autosuggest.
const languages = [
  {
    name: 'C',
    year: 1972
  },
  {
    name: 'Elm',
    year: 2012
  },
  ...
];

// Teach Autosuggest how to calculate suggestions for any given input value.
const getSuggestions = value => {
  const inputValue = value.trim().toLowerCase();
  const inputLength = inputValue.length;

  return inputLength === 0 ? [] : languages.filter(lang =>
    lang.name.toLowerCase().slice(0, inputLength) === inputValue
  );
};

// When suggestion is clicked, Autosuggest needs to populate the input
// based on the clicked suggestion. Teach Autosuggest how to calculate the
// input value for every given suggestion.
const getSuggestionValue = suggestion => suggestion.name;

// Use your imagination to render suggestions.
const renderSuggestion = suggestion => (
  <div>
    {suggestion.name}
  </div>
);

class Example extends React.Component {
  constructor() {
    super();

    // Autosuggest is a controlled component.
    // This means that you need to provide an input value
    // and an onChange handler that updates this value (see below).
    // Suggestions also need to be provided to the Autosuggest,
    // and they are initially empty because the Autosuggest is closed.
    this.state = {
      value: '',
      suggestions: []
    };
  }

  onChange = (event, { newValue }) => {
    this.setState({
      value: newValue
    });
  };

  // Autosuggest will call this function every time you need to update suggestions.
  // You already implemented this logic above, so just use it.
  onSuggestionsFetchRequested = ({ value }) => {
    this.setState({
      suggestions: getSuggestions(value)
    });
  };

  // Autosuggest will call this function every time you need to clear suggestions.
  onSuggestionsClearRequested = () => {
    this.setState({
      suggestions: []
    });
  };

  render() {
    const { value, suggestions } = this.state;

    // Autosuggest will pass through all these props to the input.
    const inputProps = {
      placeholder: 'Type a programming language',
      value,
      onChange: this.onChange
    };

    // Finally, render it!
    return (
      <Autosuggest
        suggestions={suggestions}
        onSuggestionsFetchRequested={this.onSuggestionsFetchRequested}
        onSuggestionsClearRequested={this.onSuggestionsClearRequested}
        getSuggestionValue={getSuggestionValue}
        renderSuggestion={renderSuggestion}
        inputProps={inputProps}
      />
    );
  }
}

Props

PropTypeRequiredDescription
suggestionsArrayThese are the suggestions that will be displayed. Items can take an arbitrary shape.
onSuggestionsFetchRequestedFunctionWill be called every time you need to recalculate suggestions.
onSuggestionsClearRequestedFunction*Will be called every time you need to set suggestions to [].
getSuggestionValueFunctionImplement it to teach Autosuggest what should be the input value when suggestion is clicked.
renderSuggestionFunctionUse your imagination to define how suggestions are rendered.
inputPropsObjectPass through arbitrary props to the input. It must contain at least value and onChange.
containerPropsObjectPass through arbitrary props to the container. Useful if you need to override the default props set by Autowhatever, for example, for accessibility.
onSuggestionSelectedFunctionWill be called every time suggestion is selected via mouse or keyboard.
onSuggestionHighlightedFunctionWill be called every time the highlighted suggestion changes.
shouldRenderSuggestionsFunctionWhen the input is focused, Autosuggest will consult this function when to render suggestions. Use it, for example, if you want to display suggestions when input value is at least 2 characters long.
alwaysRenderSuggestionsBooleanSet it to true if you'd like to render suggestions even when the input is not focused.
highlightFirstSuggestionBooleanSet it to true if you'd like Autosuggest to automatically highlight the first suggestion.
focusInputOnSuggestionClickBooleanSet it to false if you don't want Autosuggest to keep the input focused when suggestions are clicked/tapped.
multiSectionBooleanSet it to true if you'd like to display suggestions in multiple sections (with optional titles).
renderSectionTitleFunction
when multiSection={true}
Use your imagination to define how section titles are rendered.
getSectionSuggestionsFunction
when multiSection={true}
Implement it to teach Autosuggest where to find the suggestions for every section.
renderInputComponentFunctionUse it only if you need to customize the rendering of the input.
renderSuggestionsContainerFunctionUse it if you want to customize things inside the suggestions container beyond rendering the suggestions themselves.
themeObjectUse your imagination to style the Autosuggest.
idStringUse it only if you have multiple Autosuggest components on a page.

suggestions (required)

Array of suggestions to display. The only requirement is that suggestions is an array. Items in this array can take an arbitrary shape.

For a plain list of suggestions, every item in suggestions represents a single suggestion. It's up to you what shape every suggestion takes. For example:

const suggestions = [
  {
    text: "Apple"
  },
  {
    text: "Banana"
  },
  {
    text: "Cherry"
  },
  {
    text: "Grapefruit"
  },
  {
    text: "Lemon"
  }
];

For multiple sections, every item in suggestions represents a single section. Again, it's up to you what shape every section takes. For example:

const suggestions = [
  {
    title: "A",
    suggestions: [
      {
        id: "100",
        text: "Apple"
      },
      {
        id: "101",
        text: "Apricot"
      }
    ]
  },
  {
    title: "B",
    suggestions: [
      {
        id: "102",
        text: "Banana"
      }
    ]
  },
  {
    title: "C",
    suggestions: [
      {
        id: "103",
        text: "Cherry"
      }
    ]
  }
];

onSuggestionsFetchRequested (required)

This function will be called every time you might need to update suggestions. It has the following signature:

function onSuggestionsFetchRequested({ value, reason })

where:

  • value - the current value of the input
  • reason - string describing why onSuggestionsFetchRequested was called. The possible values are:
    • 'input-changed' - user typed something
    • 'input-focused' - input was focused
    • 'escape-pressed' - user pressed Escape to clear the input (and suggestions are shown for empty input)
    • 'suggestions-revealed' - user pressed Up or Down to reveal suggestions
    • 'suggestion-selected' - user selected a suggestion when alwaysRenderSuggestions={true}

onSuggestionsClearRequested (required unless alwaysRenderSuggestions={true})

This function will be called every time you need to clear suggestions.

All you have to do in this function is to set suggestions to [].

Note: When alwaysRenderSuggestions={true}, you don't have to implement this function.

getSuggestionValue (required)

When user navigates the suggestions using the Up and Down keys, the input value should be set according to the highlighted suggestion. You design how suggestion is modelled. Therefore, it's your responsibility to tell Autosuggest how to map suggestions to input values.

This function gets the suggestion in question, and it should return a string. For example:

function getSuggestionValue(suggestion) {
  return suggestion.text;
}

renderSuggestion (required)

Use your imagination to define how suggestions are rendered.

The signature is:

function renderSuggestion(suggestion, { query, isHighlighted })

where:

  • suggestion - The suggestion to render
  • query - Used to highlight the matching string. As user types in the input, query will be equal to the trimmed value of the input. Then, if user interacts using the Up or Down keys, the input will get the value of the highlighted suggestion, but query will remain to be equal to the trimmed value of the input prior to the Up and Down interactions.
  • isHighlighted - Whether or not the suggestion is highlighted.

It should return a string or a ReactElement. For example:

function renderSuggestion(suggestion) {
  return <span>{suggestion.text}</span>;
}

Important: renderSuggestion must be a pure function (we optimize rendering performance based on this assumption).

inputProps (required)

Autosuggest is a controlled component. Therefore, you MUST pass at least a value and an onChange callback to the input. You can pass any other props as well. For example:

const inputProps = {
  value, // usually comes from the application state
  onChange, // called every time the input value changes
  onBlur, // called when the input loses focus, e.g. when user presses Tab
  type: "search",
  placeholder: "Enter city or postcode"
};

inputProps.onChange (required)

The signature is:

function onChange(event, { newValue, method })

where:

  • newValue - the new value of the input
  • method - string describing how the change has occurred. The possible values are:
    • 'down' - user pressed Down
    • 'up' - user pressed Up
    • 'escape' - user pressed Escape
    • 'enter' - user pressed Enter
    • 'click' - user clicked (or tapped) on suggestion
    • 'type' - none of the methods above (usually means that user typed something, but can also be that they pressed Backspace, pasted something into the input, etc.)

inputProps.onBlur (optional)

The signature is:

function onBlur(event, { highlightedSuggestion })

where:

  • highlightedSuggestion - the suggestion that was highlighted just before the input lost focus, or null if there was no highlighted suggestion.

containerProps

Provides arbitrary properties to the outer div container of Autosuggest. Allows the override of accessibility properties.

const containerProps = {
  dataId: 'my-data-id'
  // ... any other properties
};

onSuggestionSelected (optional)

This function is called when suggestion is selected. It has the following signature:

function onSuggestionSelected(event, { suggestion, suggestionValue, suggestionIndex, sectionIndex, method })

where:

  • suggestion - the selected suggestion
  • suggestionValue - the value of the selected suggestion (equivalent to getSuggestionValue(suggestion))
  • suggestionIndex - the index of the selected suggestion in the suggestions array
  • sectionIndex - when rendering multiple sections, this will be the section index (in suggestions) of the selected suggestion. Otherwise, it will be null.
  • method - string describing how user selected the suggestion. The possible values are:
    • 'click' - user clicked (or tapped) on the suggestion
    • 'enter' - user selected the suggestion using Enter

onSuggestionHighlighted (optional)

This function is called when the highlighted suggestion changes. It has the following signature:

function onSuggestionHighlighted({ suggestion })

where:

  • suggestion - the highlighted suggestion, or null if there is no highlighted suggestion.

shouldRenderSuggestions (optional)

By default, suggestions are rendered when the input isn't blank. Feel free to override this behaviour.

This function gets the current value of the input and the reason why the suggestions might be rendered, and it should return a boolean.

For example, to display suggestions only when input value is at least 3 characters long, do:

function shouldRenderSuggestions(value, reason) {
  return value.trim().length > 2;
}

You can use the second reason argument to finely control exactly when the suggestions are rendered. The possible values are closely related to those for onSuggestionsFetchRequested, plus a few extra cases:

  • 'input-changed' - user typed something
  • 'input-focused' - input was focused
  • 'input-blurred' - input was un-focused
  • 'escape-pressed' - user pressed Escape to clear the input (and suggestions are shown for empty input)
  • 'suggestions-revealed' - user pressed Up or Down to reveal suggestions
  • 'suggestions-updated' - the suggestions were updated
  • 'render' - the component is re-rendering

When shouldRenderSuggestions returns true, suggestions will be rendered only when the input is focused.

If you would like to render suggestions regardless of whether the input is focused or not, set alwaysRenderSuggestions={true} (shouldRenderSuggestions is ignored in this case).

alwaysRenderSuggestions (optional)

Set alwaysRenderSuggestions={true} if you'd like to always render the suggestions.

Important: Make sure that the initial value of suggestions corresponds to the initial value of inputProps.value. For example, if you'd like to show all the suggestions when the input is empty, your initial state should be something like:

this.state = {
  value: "",
  suggestions: allSuggestions
};

highlightFirstSuggestion (optional)

When highlightFirstSuggestion={true}, Autosuggest will automatically highlight the first suggestion. Defaults to false.

focusInputOnSuggestionClick (optional)

By default, focusInputOnSuggestionClick={true}, which means that, every time suggestion is clicked (or tapped), the input keeps the focus.

On mobile devices, when the input is focused, the native keyboard appears. You'll probably want to lose the focus when suggestion is tapped in order to hide the keyboard.

You can do something like this:

<Autosuggest focusInputOnSuggestionClick={!isMobile} ... />

where isMobile is a boolean describing whether Autosuggest operates on a mobile device or not. You can use kaimallea/isMobile, for example, to determine that.

multiSection (optional)

By default, Autosuggest renders a plain list of suggestions.

If you'd like to have multiple sections (with optional titles), set multiSection={true}.

renderSectionTitle (required when multiSection={true})

When rendering multiple sections, you need to tell Autosuggest how to render a section title.

This function gets the section to render (an item in the suggestions array), and it should return a string or a ReactElement. For example:

function renderSectionTitle(section) {
  return <strong>{section.title}</strong>;
}

If renderSectionTitle returns null or undefined, section title is not rendered.

getSectionSuggestions (required when multiSection={true})

When rendering multiple sections, you need to tell Autosuggest where to find the suggestions for a given section.

This function gets the section to render (an item in the suggestions array), and it should return an array of suggestions to render in the given section. For example:

function getSectionSuggestions(section) {
  return section.suggestions;
}

Note: Sections with no suggestions are not rendered.

renderInputComponent (optional)

You shouldn't specify renderInputComponent unless you want to customize the rendering of the input.

To keep Autosuggest accessible, renderInputComponent MUST:

  • render an input
  • pass through all the provided inputProps to the input

Example:

const renderInputComponent = inputProps => (
  <div>
    <input {...inputProps} />
    <div>custom stuff</div>
  </div>
);

Note: When using renderInputComponent, you still need to specify the usual inputProps. Autosuggest will merge the inputProps that you provide with other props that are needed for accessibility (e.g. 'aria-activedescendant'), and will pass the merged inputProps to renderInputComponent.

renderSuggestionsContainer (optional)

You shouldn't specify renderSuggestionsContainer unless you want to customize the content or behaviour of the suggestions container beyond rendering the suggestions themselves. For example, you might want to add a custom text before/after the suggestions list, or to customize the scrolling behaviour of the suggestions container.

The signature is:

function renderSuggestionsContainer({ containerProps, children, query })

where:

  • containerProps - props that you MUST pass to the topmost element that is returned from renderSuggestionsContainer.
  • children - the suggestions themselves. It's up to you where to render them.
  • query - Same as query in renderSuggestion.

For example:

function renderSuggestionsContainer({ containerProps, children, query }) {
  return (
    <div {...containerProps}>
      {children}
      <div>
        Press Enter to search <strong>{query}</strong>
      </div>
    </div>
  );
}

When renderSuggestionsContainer returns a composite component (e.g. <IsolatedScroll ... /> as opposed to a DOM node like <div ... />), you MUST call containerProps.ref with the topmost element that the composite component renders.

For example:

import IsolatedScroll from "react-isolated-scroll";

function renderSuggestionsContainer({ containerProps, children }) {
  const { ref, ...restContainerProps } = containerProps;
  const callRef = isolatedScroll => {
    if (isolatedScroll !== null) {
      ref(isolatedScroll.component);
    }
  };

  return (
    <IsolatedScroll ref={callRef} {...restContainerProps}>
      {children}
    </IsolatedScroll>
  );
}

theme (optional)

Autosuggest comes with no styles.

It uses react-themeable that allows you to style your Autosuggest component using CSS Modules, Radium, Aphrodite, JSS, Inline styles, and global CSS.

For example, to style the Autosuggest using CSS Modules, do:

/* theme.css */

.container { ... }
.input { ... }
.suggestionsContainer { ... }
.suggestion { ... }
.suggestionHighlighted { ... }
...
import theme from "theme.css";
<Autosuggest theme={theme} ... />

When not specified, theme defaults to:

{
  container:                'react-autosuggest__container',
  containerOpen:            'react-autosuggest__container--open',
  input:                    'react-autosuggest__input',
  inputOpen:                'react-autosuggest__input--open',
  inputFocused:             'react-autosuggest__input--focused',
  suggestionsContainer:     'react-autosuggest__suggestions-container',
  suggestionsContainerOpen: 'react-autosuggest__suggestions-container--open',
  suggestionsList:          'react-autosuggest__suggestions-list',
  suggestion:               'react-autosuggest__suggestion',
  suggestionFirst:          'react-autosuggest__suggestion--first',
  suggestionHighlighted:    'react-autosuggest__suggestion--highlighted',
  sectionContainer:         'react-autosuggest__section-container',
  sectionContainerFirst:    'react-autosuggest__section-container--first',
  sectionTitle:             'react-autosuggest__section-title'
}

The following picture illustrates how theme keys correspond to Autosuggest DOM structure:

DOM structure

id (required when multiple Autosuggest components are rendered on a page)

The only reason id exists, is to set ARIA attributes (they require a unique id).

When rendering a single Autosuggest, don't set the id (it will be set to '1', by default).

When rendering multiple Autosuggest components on a page, make sure to give them unique ids. For example:

<Autosuggest id="source" ... />
<Autosuggest id="destination" ... />

Development

npm install
npm start

Now, open http://localhost:3000/demo/dist/index.html and start hacking!

License

MIT