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

former-kit-skin-pagarme

v2.17.3

Published

A skin for former-kit based on Pagar.me's brand

Downloads

489

Readme

Pagar.me Skin for FormerKit

Our style guide as a FormerKit skin

Join the chat at https://gitter.im/pagarme/opensource

Using

This skin is based on our component style guide and built to work with FormerKit Dashboard setup. To use it, you need to set some configurations on Webpack and install some packages.

You can follow it here.

Development

To build a npm-ready package:

yarn build

In real life you will probably want to see changes made in this skin package in an already existing application.

To register the skin as a "linkable" package, run the following command in the skin directory:

yarn link

Then, in an existing application link the registered package:

yarn link former-kit-skin-pagarme

To keep watching for changes:

yarn start

Publishing to NPM

The publishing process is automated using a combination of GitHub Actions and CircleCI. We're using the release-please-action in order to automatically create GitHub releases and bump the package.json version based on commit messages conventions known as Conventional Commits. And on Circle CI we have the NPM publishing workflow.

By following those commit conventions the release-please-action will automatically identify when you're merging a pull request which is in accordance and immediately after will create another pull request which will contain the changelog, the package.json version bump, a tag, and a release indicating the new version.

You're not required to merge this release pull request, but when you do it will trigger a workflow on CircleCI which will publish the new version of the package to NPM.

if you can't get it through CI you need to have access to NPM publish and run

npm publish

Licensing

See LICENSE.