npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

solid-base-components

v0.2.0

Published

Components for solid

Downloads

7

Readme

solid-base-components

This is a collection of barely styled components on which you can build your own design system. It tries to use more consistent patterns for all input elements to make development easier.

Commonly used non-native elements are also implemented, such as popovers with arrow, and more to come.

Demo

Installation

npm install solid-base-components

Usage

import { render } from 'solid-js/dom'
import { Box, Input, InputFile, Select, Popover, Checkbox, Radio } from 'solid-base-components';
// Minimally required layout styles
import 'solid-base-components/dist/build.css'

const App = () =>
  <Box vertical>
    <Input onChange={text => console.log(text)} />
    <InputFile onChange={files => console.log(files)}>Add File</InputFile>
    <Box horizontal>
      <Select
        options={options}
        value={1}
        onChange={console.log}
      />
      <Popover
        arrow
        closeOnClick
        trigger={({ ref, open }) =>
          <Button ref={ref} onClick={toggle}}>
            Click Me
          </Button>
        }
      >
        <div>Content</div>
      </Popover>
    </Box>
    <Box horizontal>
      <Checkbox onChange={isChecked => console.log(isChecked)}>
        Check Me
      </Checkbox>
      <Radio.Group
        name='number'
        options={options}
        value={1}
        onChange={console.log}
      />
    </Box>
  </Box>

render(() => App, document.getElementById('app'))

Styling

You are expected to provide your own styles for components. They follow a strict BEM convention.

For example, to add button styles:

<Button size='small' variant='primary'>
  Click Me
</Button>
/* This would be your own CSS */
.Button {
  border: 2px solid black;
}
.Button--small {
  height: 20px;
}
.Button--primary {
  color: white;
  background-color: blue;
}

See the styling documentation for more details.

Icons

Icons use octicons for now. You can use them directly or on input/buttons:

<Icon name='gear' />
<Input icon='search' iconAfter='sync' />
<Button icon='search' iconAfter='sync'>Click Me</Button>

Icons

<Icon /> also takes props info, success, warning or danger for colors.

Conventions

User-input elements try to follow these conventions:

  • If props.value didn't change, keep the value in sync with the DOM, to bring the behavior closer to React.
  • Have a loading: boolean property that sets the element to disabled and displays a spinning loading icon.
  • Choice picking components (Select, Radio.Group, Dropdown) take an options: Option[] property, where Option is { value: string|number|null, label: JSX.Element }.
  • Have an onChange(value: any, ev: Event) handler, where the first argument is the new value. If it's a choice-picking component, the Option is passed as a third argument.