Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

former-kit-skin-pagarme

Package Overview
Dependencies
Maintainers
0
Versions
90
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

former-kit-skin-pagarme

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

  • 2.17.3
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
109
increased by890.91%
Maintainers
0
Weekly downloads
 
Created
Source

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.

FAQs

Package last updated on 02 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc