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

vh-os-packages

v0.0.1-76

Published

All Components are made using [ReactJS](https://reactjs.org/) and [Styled Components](https://styled-components.com/) and we use [Storybook](https://storybook.js.org/) as a rendering

Downloads

19

Readme

This is the VanHack OpenSource project

All Components are made using ReactJS and Styled Components and we use Storybook as a rendering

Release Current

master

Prototype

You can see the prototype here

Instructions

1 - Reuse as much as you can

2 - Create as many components as you need thinking that could be reused

3 - Don't forget to cover the [LOADING, ERROR and SUCCESS] states

4 - We want to see your tests!!!

How to contribute:

  • Create a Fork on Github
  • Keep your fork up to date
  • Create a new branch from Open RC (Release Current) not from MASTER
  • Commit on your own fork
  • Create a pull request to Open RC (Release Current) not against MASTER

How to run:

  • Clone the project
  • run yarn install
  • run yarn add styled-components install styled componets but discard the changes on package.json because the styled components must be installed as peerDependence
  • run yarn start
  • The project will run at the port http://localhost:6007

Architecture:

ROOT                      #STORYBOOK CONFIG
│
└───assets
│   └───icons                  # Put all icons inside
└───packages
│   └───Colors                 # Colors configuration
│   └───Grid                   # Grid configuration we must use this component to create all components grid
|   └───Components
|       └───[YOUR COMPONENT FOLDER]# Create your component here with the name
|       └───input              # All inputs should be created inside input folder
|           └───Simple         # A simple component
|               └───.spec.js   # All tests should be written in this file
|               └───index.jsx  # The component implementation
|               └───stories.js # The component stories for the Storybok
|               └───styles.js  # If needed all component styles should be here
|
└─── .babelrc                   # BABEL CONFIGURATION
└─── package.json               # PACKAGE JSON ***(Don't commit the package.json ever)**
└─── README.md                  # README.md Changes are welcome

Mandatory

All components must be created inside packages/Components

If you have any question, please ask on the slack and we'll help you.

Big Thanks and WeHackTogether!!!