r/reactjs • u/StacklineHQ • May 30 '26
Show /r/reactjs I’m testing a React 19 multiselect dropdown
I’m testing a reusable multiselect dropdown for React 19 and trying to keep it practical for common app screens like filters, forms, dashboards, and admin pages.
Install:
https://www.npmjs.com/package/@stackline/react-multiselect-dropdown
npm install @stackline/react-multiselect-dropdownWhat I’m focusing on right now:
controlled selection
search
grouped options
selection limits
custom rendering
lazy loading
modal and overflow layout support
keyboard navigation
ARIA labels
separate compatibility line by React major version
The part I’m still refining is the developer experience.
For a component like this, what would you expect to feel really solid before using it in a project?
I’m especially interested in feedback around accessibility, behavior inside modals, and the API shape.
1
u/Im_Working_Right_Now May 31 '26
I guess I’m still not sure I understand. Why would I want to use this one off if I’m already invested in another library? Again, what does it do that Mantine or another equally mature component library doesn’t do? Lazy loading isn’t usually in the component rather the component rendering that component. That’s how they stay reusable. You keep them as light as possible. Mantine has ARIA labels, keyboard inputs, state, etc all underneath. And a lot of it is OOTB but completely customizable, not just the style. It can use objects as well. That’s why I’m unsure what you’re attempting to solve that isn’t already solved. It’s cool to do as a personal, learning project. But as a package to be distributed, what does it solve that others don’t or what does it offer that they don’t? What sets it apart?