bolster-css - npm Package Compare versions

Comparing version 0.1.0 to 0.1.1

package.json

@@ -68,9 +68,9 @@ {
     "build-docs": "NODE_ENV=production node ./node_modules/webpack/bin/webpack.js --progress --colors --config=webpack.config.build-docs.js",
-    "compile-for-publish": "npm run lint && npm run compile-sass && npm run build-docs",
     "compile-sass": "NODE_ENV=production node ./compile-sass.js",
+    "compile-with-docs": "npm run lint && npm run compile-sass && npm run build-docs",
     "dev": "NODE_ENV=development node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --config=webpack.config.dev.js",
     "lint": "NODE_ENV=test ./node_modules/eslint/bin/eslint.js src",
-    "prepublish": "in-publish && npm run compile-for-publish || in-install"
+    "prepublish": "in-publish && npm run compile-sass || in-install"
   },
-  "version": "0.1.0"
+  "version": "0.1.1"
 }

README.md

@@ -203,7 +203,7 @@ # bolster-css
 * `compile-sass` => Compiles the SCSS files into CSS files in the `css` folder, as well as complete files in `dist`
-* `compile-for-publish` => runs the `lint`, `compile-sass`, and `build-docs` scripts
+* `compile-with-docs` => runs the `lint`, `compile-sass`, and `build-docs` scripts
 * `dev` => runs the webpack dev server for the playground
 * `lint` => runs ESLint against files in the `src` folder
-* `prepublish` => if in publish, runs `compile-for-publish`
+* `prepublish` => if in publish, runs `compile-sass`
 
 Happy `bolster`ing!

Fixed alerts

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Improved metrics

Number of low supply chain risk alerts

0

-100%

Worsened metrics

Total package byte prevSize

267280

-95.67%

Number of package files

33

-47.62%

Lines of code

6624

-56.61%

No dependency changes