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

befish-ui-ts

v1.0.0

Published

This project skeleton was created to help people get started with creating their own React component library using:

Downloads

3

Readme

React Component Library

This project skeleton was created to help people get started with creating their own React component library using:

Read my blog post about why and how I created this project skeleton ▸

Development

Testing

npm run test

Building

npm run build

Storybook

npm run storybook

Installing component library locally

Let's say you have another project (test-app) on your machine that you want to try installing the component library into without having to first publish the component library. In the test-app directory, you can run:

npm i --save ../react-component-library

which will install the local component library as a dependency in test-app. Your components can then be imported and used.

Publishing

First make sure that you've updated the name field in package.json to reflect your NPM package name in your private or public NPM registry. Then run:

npm publish

Component Usage

Let's say you created a public NPM package called harvey-component-library with the TestComponent component created in this repository.

Usage of the component (after the library installed as a dependency into another project) will be:

import React from 'react';
import { TestComponent } from 'harvey-component-library';

const App = () => (
  <div className='app-container'>
    <h1>Hello I'm consuming the component library</h1>
    <TestComponent theme='primary' />
  </div>
);

export default App;

Using internal SASS variables

I've found that it's helpful to export SASS variables to projects consuming the library. As such, I've added the rollup-plugin-copy NPM package and used it to copy the typography.scss and variables.scss into the build directory as part of the Rollup bundle process. This allows you to use these variables in your projects consuming the component library.

For example, let's say you installed harvey-component-library into your project. To use the exported variables/mixins, in a SASS file you would do the following:

@import '~harvey-component-library/build/typography';

.example-container {
    @include heading;

    color: $harvey-white;
}

LISTA DE COMPONENTES A PASAR:

FORM:

  1. TextField
  2. AreaField
  3. PasswordField
  4. IntField
  5. DecimalField
  6. TimePicker
  7. DatePicker
  8. SwichInput
  9. RadioInput ( JSON CON OPCIONES CADA UNA DIBUJA UN RADIO)
  10. CheckBoxInput
  11. SelectInput (simple and multiple)
  12. AutoCompleteInput (simple and multiple)
  13. ColorInput

FORM NICE TO HAVE:

  1. DateTimePicker
  2. DateRangePicker

BUTTONS:

  1. containedButton
  2. outlinedButton
  3. linkButton
  4. floatButton (simple and menu)

BUTTONS NICE TO HAVE:

  1. iconButton

ADMIN LAYOUT:

  1. Header
  2. Menu
  3. Container
  4. Footer

ACLARACIONES:

  1. Funcional Components.
  2. Use memo
  3. todo hooks

TESTING

  1. https://enzymejs.github.io/enzyme/
  2. https://npmjs.com/package/chai
  3. https://www.npmjs.com/package/mocha
  4. https://sinonjs.org/
  5. https://www.npmjs.com/package/nyc
  6. https://www.npmjs.com/package/nock