employer-style-base
Advanced tools
Comparing version 2.2.1 to 2.2.5
{ | ||
"name": "employer-style-base", | ||
"version": "2.2.1", | ||
"version": "2.2.5", | ||
"author": "EmployerSiteContentProducts@cb.com", | ||
@@ -5,0 +5,0 @@ "license": "Apache-2.0", |
@@ -9,6 +9,6 @@ # employer-style-base | ||
Install with Bower (from an appropriate repository) | ||
Add and install with Yarn: | ||
```sh | ||
$ bower install employer-style-base | ||
$ yarn add employer-style-base | ||
``` | ||
@@ -19,6 +19,7 @@ | ||
```scss | ||
@import 'bower_components/bourbon/app/assets/stylesheets/bourbon'; | ||
@import 'bower_components/employer-style-base/sass/base'; | ||
@import 'bourbon/app/assets/stylesheets/bourbon'; | ||
@import 'employer-style-base/sass/base'; | ||
@import 'some-grid-foundation'; | ||
@import 'my-app'; | ||
@import 'your-app'; | ||
``` | ||
@@ -34,3 +35,3 @@ | ||
At the moment, only uncompiled Sass source files are available for consumption. That means your application will need to perform the precompilation, whether it be through Gulp, Grunt, Rails asset pipeline, etc. Do note that `employer-style-base` depends upon, and includes [Bourbon](http://bourbon.io/) for basic Sass mixins. Additionally, this library includes its own reset, scoped to `employer-scope`. | ||
At the moment, only uncompiled Sass source files are available for consumption. That means your application will need to perform the precompilation, whether it be through Webpack, Gulp, Grunt, Rails asset pipeline, etc. Do note that `employer-style-base` depends upon and includes [Bourbon](http://bourbon.io/) for basic Sass mixins. Additionally, this library includes its own reset, scoped to `employer-scope`. | ||
@@ -55,9 +56,11 @@ The current layout of this library is heavily inspired by [Bitters](http://bitters.bourbon.io/), a wonderful boilerplate of common-sense Sass conventions and structure. Our outline looks a little something like this: | ||
After your PR is merged, add a [release](https://github.com/cb-talent-development/employer-style-base/releases) and update the [semantic version number appropriately](http://semver.org/). | ||
After your PR is merged, update the [semantic version number appropriately](http://semver.org/), add a [release](https://github.com/cb-talent-development/employer-style-base/releases) and `publish` via Yarn or npm. | ||
Then update the `bower.json` file in your repo with the new number. | ||
Then update the `package.json` file in your project with the new version: | ||
```json | ||
"dependencies": { | ||
"employer-style-base": "=2.2.1" | ||
} | ||
``` | ||
"employer-style-base": "=1.0.0" | ||
``` | ||
@@ -67,2 +70,1 @@ ### Future | ||
- Implement build process to compile CSS into `dist` for easy consumption | ||
- Remove `bourbon` dependency |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
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
92318
66
2