sass-true - npm Package Compare versions

Comparing version 2.0.2 to 2.0.3

bower.json

 {
   "name": "true",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "main": "sass/_true.scss",
@@ -5,0 +5,0 @@ "description": "Unit testing for Sass.",

package.json

 {
   "name": "sass-true",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "description": "Unit testing for Sass.",
@@ -22,3 +22,3 @@ "homepage": "http://ericsuzanne.com/true",
     "css-selector-parser": "~1.0.0",
-    "node-sass": "^3.0.0",
+    "node-sass": "^3.4.0",
     "underscore": "~1.7.0"
@@ -33,2 +33,3 @@ },
   "eyeglass": {
+    "name": "true",
     "exports": "eyeglass-exports.js"
@@ -35,0 +36,0 @@ },

README.md

@@ -32,2 +32,3 @@ True
 
+
 Usage
@@ -75,2 +76,16 @@ -----
 
+**Note:**
+Function unit-tests work across the board,
+but testing mixins can be a bit more complex.
+At this point,
+only Mocha is able to compare/report the results of mixin tests,
+as long as the mixins don't manipulate the selector chain
+(it can't test media-query mixins for example).
+Without using Mocha,
+you can test any mixin,
+but you will have to compare the expected and actual results manually
+in the output code.
+Version control can make that much easier than it sounds.
+
+
 ### With node-sass and Mocha (or other JS test runners)
@@ -86,6 +101,6 @@
    var path = require('path');
-   var true = require('sass-true');
+   var sassTrue = require('sass-true');
 
    var sassFile = path.join(__dirname, 'test.scss');
-   true.runSass({file: sassFile}, describe, it);
+   sassTrue.runSass({file: sassFile}, describe, it);
    ```
@@ -107,2 +122,3 @@
 
+
 ### With ruby-sass on the command line
@@ -109,0 +125,0 @@

No alert changes

Improved metrics

Total package byte prevSize

436640

increased by0.12%

Number of lines in readme file

156

increased by11.43%

Dependency changes

• Updatednode-sass@^3.4.0