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

gaiden

v24.3.4

Published

Styleguide for GetNinjas projects

Downloads

79

Readme

Gaiden Logo

Codacy Badge npm version

GetNinjas Styleguide - https://getninjas.github.io/gaiden

Quick Start

  • Clone the repository: git clone https://github.com/getninjas/gaiden.git
  • Install dependencies with: npm install
  • Configure the build links with: npm run config

Build Process

The npm run build command, generated files into the dist folder, separated themes file.

Release process

We are using npm version to generate our releases. There are 3 kind of releases generally used: major, minor and patch. See the http://semver.org/ for more details.

The process is:

  1. After merge PR on master:

    git checkout master
    git pull --tags origin master
  2. Run npm run version command.

  3. Run npm version major|minor|patch -m "Message of your changes" (important: you need to be an admin to push on master).

  4. Now let's publish the package on npm:

    1. If you not have access to Org GetNinjas in NPM, you need ask for users in Org to add you.
    2. If nothing fails on npm version and you have the credentials of npm GetNinjas account, run npm publish.
  5. Done! Now, you can install the package on any project!

Deploy to gh-pages

  1. Run npm run deploy-storybook to publish static site in gh-pages;

  2. Access this link https://getninjas.github.io/gaiden/ and enjoy it!

Commands

Here are a description of the scripts that we have in the project:

| Script | Description | |------------------|-------------------------------------------------------------------------------------------------------------| | storybook | Start storybook for development purposes | | build-storybook | Build storybook for deploy. The output is in docs folder | | deploy-storybook | Deploy storybook in github-pages | | version | Build the project and add the dist folder to git stage | | postversion | Script that runs after the version (due to naming conventions). Push the changes and the tags to the branch | | build | Build the library |