@thisbeyond/solid-select

• Built for Solid: leverages fine-grained reactivity primitives for coordination.
• Flexible: built to support a wide range of cases, from single selects to multi-select autocomplete lists.
• Extendable: use the pre-fabricated components or build your own from the core primitives.
• Zero dependencies: Just pair with Solid and good to go.

How do I get started? 🧭

Install it:

npm install @thisbeyond/solid-select

Use it:

import { Select } from "@thisbeyond/solid-select";
import "@thisbeyond/solid-select/style.css";

const App = () => {
  return (
    <div>
      <Select options={["apple", "banana", "pear", "pineapple", "kiwi"]} />
    </div>
  );
};

export default App;

See more examples at https://solid-select.com

What's implemented? ✔️

• A high level Select component that can be configured with either a static or dynamic list of options.
• Support for single value selection or multiple value selection.
• createOptions helper for configuring filterable options based on input value (complete with match highlighting). Works with lists of plain strings or can be passed a 'key' to filter against lists of objects. Can also be used to configure creating new options on the fly.
• Opt-in sensible default styling. Customise easily or style from scratch.
• Composable building blocks to create your own control.
• Lower level createSelect primitive if you just want the core logic.

Who made this? ✍

Martin Pengelly-Phillips

Why did you make it?

I've been part of the SolidJS community for a while now and one of the things I really like is the emphasis on trying things out and sharing them (https://hack.solidjs.com). The ecosystem is small which creates a lot of opportunity and a lower barrier to entry for sharing I find.

I published my first Solid library (https://solid-dnd.com) a short while back as a first dabble in sharing what I had learnt on a personal project. That went well so when I had to create a multi-select autocomplete control for another personal project I knew I'd be sharing that too - and so Solid Select came to be :)

Changelog

[0.14.0] - 2023-04-09

A major refactor to more clearly separate out the core and the builtin components. The builtin Select and accompanying component interfaces remains unchanged, but there are backwards incompatible changes to the createSelect interface.

Changed

• Breaking Change Streamline the core and allow greater control in components. No longer pass or use element refs in the core, including not automatically settign up event handlers. Instead, return commonly useful handlers (such as onKeyDown) from createSelect for use in components.

• Breaking Change Expose signals directly as accessors rather than hiding behind property getters in return of createSelect. For example, select.options should now be select.options(). This more closely matches SolidJS and avoids inconsistency around not being able to set properties directly.

• Breaking Change Remove helpers (such as open and close) in favour of exposing setters (e.g. setIsOpen) consistently from createSelect. This provides a more intuitive interface rather than some aspects having helpers and others not.

• Breaking Change Refactor Select components to make use of a shared Context providing the created select. Avoid unnecessary prop drilling and make it easier to others to compose their own selects (with useSelect).

• Breaking Change Make createAsyncOptions throttle by default. The fetcher will be called every 250ms by default to prevent excessive calls to resources. The threshold can be configured or removed by passing a second argument - e.g. createAsyncOptions(fetcher, 0) for original behaviour.

• Hide the input caret with CSS rather than hide the entire input component to make some logic easier (such as focus handling).

Fixed

• Allow repositioning the cursor on active input text. Previously, attempting to do this would clear the input value.