node-sass - npm Package Compare versions

Comparing version 1.1.1 to 1.1.2

build.js

@@ -47,3 +47,3 @@ #!/usr/bin/env node
 
-    mocha.addFile(path.resolve(__dirname, 'test', 'test.js'));
+    mocha.addFile(path.resolve(__dirname, 'test', 'api.js'));
 
@@ -53,3 +53,3 @@ mocha.run(function () {
       if ((total - failures) * 100 / total < 90) {
-        console.log('Problem with the binary; manual build incoming');
+        console.log('Problem with the binary: ' + failures + ' of ' + total + ' tests are failing.\nManual build incoming');
         console.log('Please consider contributing the release binary to https://github.com/sass/node-sass-binaries for npm distribution.');
@@ -56,0 +56,0 @@ build();

CONTRIBUTING.md

@@ -0,0 +0,0 @@ ## Contributing

lib/cli.js

@@ -0,0 +0,0 @@ var watch = require('node-watch'),

lib/render.js

@@ -0,0 +0,0 @@ var sass = require('../sass'),

libsass/Readme.md

@@ -0,0 +0,0 @@ Libsass

package.json

@@ -5,3 +5,3 @@ {
   "description": "wrapper around libsass",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "homepage": "https://github.com/sass/node-sass",
@@ -8,0 +8,0 @@ "keywords": [

README.md

@@ -0,0 +0,0 @@ # node-sass

sass.js

@@ -0,0 +0,0 @@ var path = require('path');

test/api.js

@@ -0,0 +0,0 @@ var assert = require('assert'),

test/cli.js

@@ -0,0 +0,0 @@ var assert = require('assert'),

test/sass-spec/README.md

@@ -0,0 +0,0 @@ sass-spec

test/sass-spec/spec/basic/12_pseudo_classes_and_elements/notes.txt

@@ -0,0 +0,0 @@ Original Sass and libsass can produce different output for functional pseudo-classes. Original Sass does not normalize whitespace contained within an expression, and it also accepts invalid expressions. Libsass is stricter, and removes superfluous whitespace. E.g., on the following selector:

test/spec.js

@@ -0,0 +0,0 @@ var assert = require('assert'),

test/util/index.js

@@ -0,0 +0,0 @@ var fs = require('fs'),

New alerts

License Policy Violation

License

This 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 risk

A 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

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

31546798

increased by46.84%

Number of package files

1614

increased by0.06%

Lines of code

22204

increased by0.04%

Worsened metrics

Number of medium supply chain risk alerts

4

increased by33.33%

No dependency changes