@clearkit/one
Advanced tools
Comparing version 0.31.1 to 0.31.2
{ | ||
"name": "@clearkit/one", | ||
"version": "0.31.1", | ||
"version": "0.31.2", | ||
"description": "ClearKit One", | ||
@@ -55,3 +55,3 @@ "main": "dist/clearkit-one.js", | ||
"type": "git", | ||
"url": "git+https://dizzyup@github.com/dizzyup/clearkit-one.git" | ||
"url": "https://github.com/clearbit/clearkit-one/" | ||
}, | ||
@@ -58,0 +58,0 @@ "author": "@dizzyup @mginnard @mattrothenberg", |
# ClearKit One | ||
### What's happening in this repo? | ||
## What's happening in this repo? | ||
@@ -19,3 +19,3 @@ This repo takes the Tailwind config and the CSS variables stylesheet from the | ||
### Initial setup | ||
## Initial setup | ||
@@ -26,3 +26,3 @@ 1. Clone this repo. | ||
### Developing clearkit-one.css | ||
## Developing clearkit-one.css | ||
@@ -58,4 +58,11 @@ Running `$ yarn start` kicks off the following process: | ||
### Write new blueprints | ||
## Releasing & publishing new versions to npm | ||
[TODO] | ||
We use the tool [`np`](https://github.com/sindresorhus/np) (installed globally) for deploying new versions of the library. | ||
When you're ready to deploy and your changes are pushed to master, run `np` and it will walk you through the steps: | ||
- Verifying tests pass | ||
- Choosing a new version number | ||
- Auto-tagging and release notes | ||
- Publishing to NPM |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
1917608
82781
66
1