Why is there no input component?

[azzazkhan]

I've noticed that neither Bits UI not it's parent Melt UI has input component though ShadCN Svelte which is based on Bits UI has one.

[huntabyte]

Why would it have an input component? What functionality would a headless library provide to an input that doesn't come out of the box with <input />

[azzazkhan]

Well, it would be better to have a component which would encapsulate error state, helper text, icons, and other useful states. Like adding a <p> tag below the input and manually hiding/showing it for error state would be a cumbersome when we got a lot of inputs on the page. It would be great if we could just pass an error prop to a component and it places it in correct place.

[riziles]

@azzazkhan , it's worth noting that bits has lots of awesome input components like combobox, date picker, pin input, drop down, etc, that wrap the vanilla html input element, but you could always still use it directly.

[azzazkhan]

I'm looking for something similar to ShadCN Svelte but in Bits UI design, an input component that could handle icons, error states, helper text and other necessary states. Also I just noticed there's no text area component either, it would be great if there would be one with auto height.

[riziles]

@azzazkhan, auto scaling the height of a textarea element is a function of styling, but as @huntabyte pointed out, bits is intentionally an unstyled component library.