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

@valudio/ui

v1.2.10

Published

## Usage

Downloads

17

Readme

@valudio/ui · Release npm version

Usage

In order to theme the components the provider should be added wrapping your app.

import { Provider } from '@valudio/ui'

<Provider theme={ theme }>
  <App />
</Provider>

Development

Base props implementation

All component should use or extend the IBaseProp on it's props.

isHidden prop should be used like:

const Component: React.FC<IProps> = ({ isHidden, ...props }) => {
  ...
  if (isHidden) return null 
  ...
}

className prop should be used like:

const Component: React.FC<IProps> = ({ className, ...props }) => {
  ...
  return <Styled { ...props } className={ className }>...</Styled>
}

style prop should be used like:

const Component: React.FC<IProps> = ({ style, ...props }) => {
  ...
  return <Styled { ...props } style={ style }>...</Styled>
}

Externally reseting values

Components are designed to avoid controlling their state externally on your containers or pages. For example, you can't pass values to them, only it's initial value and options (in the case of a Select or MultiSelect). In other words, they manage their own state and just send it's value when there's change.

So, if you want to reset their internal state you should do the next:

const Component: React.FC<IProps> = ( => {
  const [ form, setForm ] = useState<HTMLFormElement>()
  const handleClear = event => {
    event.preventDefault()
    ref.reset()
  }
  ...
  return (
    <...>
      <form ref={ setForm }>
        <button onClick={ handleClear }>Reset</button>
        <Select { ... } form={ form } />
      </form>
    </...>
  )
}

Note that the ref is not managed with a useRef hooks since it doesn't re-render the component.

Debugging

In order to run locally, internally using yarn for now.

npm i or yarn install

npm run storybook or yarn storybook