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

mycomponentbase-test

v0.2.0

Published

An opinionated structure for reusable and declouped react components.

Downloads

1

Readme

React component base

Stack

Getting Started

Installation

First of all, install the dependencies to run this boilerplate.

# install dependencies
$ npm install

Folders and Files

├── css
│   └── main.css
├── dist
│   └── Foo.js
├── src
│   └── Foo.js
├── stories
│   └── Foo.js
├── storybook
│   ├── config.js
│   └── webpack.config.js
├── tests
│   ├── helpers
│   │   └── setup.js
│   └── specs
│       └── Foo.spec.js
├── .babelrc
├── .editorconfig
├── .eslintrc
├── .gitignore
├── .npmignore
├── Readme.md
└── package.json

How to Develop with Storybook

Create your storybook stories on stories folder. If you want to create another story file, remember to load on .storybook/config.js. With all stories, just run npm run storybook to open your isolated environment.

If you want to know more about storybook, see this link.

Code Standarts

This project uses eslint and .editorconfig is defined to have indent_size of 4 spaces.

This project also uses Husky to prevent push messy and wrong code. Please, don't be stupid, fix all errors before push =D

Tasks

  • npm run build: build component to external use.
  • npm run publish: build and publish the component to npm.
  • npm run storybook: launch storybook to develop your component.
  • npm run build-storybook: build an static storybook to .out folder.
  • npm run deploy-storybook: build and deploy a storybook with component to gh-pages.
  • npm run test: run all specs.
  • npm run test:tdd: run all specs and watch.
  • npm run test:coverage: run all specs and coverage.
  • npm run lint: lint all files searching for errors.
  • npm run lint:fix: fix some lint errors.

License

MIT License @ Willian Justen