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

@elemental-ui-alpha/field

v0.0.2

Published

The field package exposes the elements around form inputs, and an API to compose them.

Downloads

5

Readme

Field

import { Field, FieldDescription, FieldLabel, FieldMessage } from '@elemental-ui-alpha/field';

Field

The Field component is lower level building block for generating custom components.

Using a render prop, the field component connects the label, description, and message to the input element.

<Field
  label="Field label"
  description="We will never share your information with third parties"
  message="This field is required"
>
  {({ inputProps }) => <TextInput {...inputProps} />}
</Field>

Elements

If the layout of the Field component doesn't work for you, or for any other reason, you can compose the elements below in a way that suites. Please be mindful to maintain accessibility.

FieldDescription

A styled div element, intended to describe the field's intention.

<FieldDescription>
  Provide additional information, where the label will not suffice.
</FieldDescription>

FieldLabel

A styled label element

<FieldLabel>Field label</FieldLabel>

FieldMessage

A styled div element, intended to provide users with a "tonal" message within the context of a field.

<>
  <FieldMessage>A neutral message</FieldMessage>
  <FieldMessage tone="positive">A positive message</FieldMessage>
  <FieldMessage tone="critical">A critical message</FieldMessage>
</>

Composition

You must maintain accessibility when composing the elements yourself to create a custom component.

let [value, setValue] = useState('');
let [touched, setTouched] = useState(false);

let inputId = 'composed-input';
let messageId = 'composed-message';
let descriptionId = 'composed-description';
let isInvalid = !value && touched;

return (
  <Columns
    columns={8}
    gap={['small', null, null, null, 'xxlarge']}
    collapse="xlarge"
  >
    <Column span={3}>
      <FieldLabel htmlFor={inputId}>Email</FieldLabel>
      <FieldDescription id={descriptionId}>
        Use your company email
      </FieldDescription>
    </Column>
    <Column span={5}>
      <TextInput
        aria-describedby={isInvalid ? messageId : descriptionId}
        id={inputId}
        name="email"
        onBlur={() => setTouched(true)}
        onChange={e => setValue(e.target.value)}
        type="email"
        value={value}
      />
      {isInvalid && (
        <FieldMessage id={messageId} tone="critical">
          The email field is required
        </FieldMessage>
      )}
    </Column>
  </Columns>
);