voodoo - npm Package Compare versions

Comparing version 0.0.4 to 0.0.5

CHANGELOG.md

@@ -0,3 +1,7 @@
+## v0.0.41 - 25/01/2012
+* added -b, --base <path> cli param
+* setup testing env
+
 ## v0.0.4 - 25/01/2012
-* added -f, --force cli param
+* added -f, --force cli param, so users can stop on build step errors/warnings
 * cleaned up npm dependencies
@@ -4,0 +8,0 @@

config.js

@@ -8,10 +8,5 @@ config.init({
   concat: {
-
     // The core library files
     "assets/js/libs.js": [
-      "assets/js/libs/dd_belatedpng.js",
-      "assets/js/libs/jquery-1.7.1.min.js",
-      "assets/js/libs/less.js",
-      "modernizr-2.0.6.min.js",
-      "selectivizr.js"
+      "assets/js/libs/*.js"
     ],
@@ -21,41 +16,12 @@
     "assets/js/app.js": ["assets/js/*.js"],
+  },
 
-    // Your CSS
-    // TODO: we won't need this I guess, since
-    // we already have a strong include system within
-    // our style.less, so generally we stick with one css ?
-    // "dist/debug/css/style.css": ["assets/css/*.css"]
-  },
-  
-  // TODO: how do we work on this, in combo with the concat?
-  // I am guessing: first minify to name.min.js, than add that
-  // min to the concat? Or the other way around?
   min: {
-    "dist/release/js/libs.js": ["dist/debug/js/libs.js"],
-    "dist/release/js/app.js": ["dist/debug/js/app.js"],
-    "dist/release/js/templates.js": ["dist/debug/js/templates.js"]
+    "assets/js/libs.js": ["assets/js/libs.js"],
+    "assets/js/app.js": ["assets/js/app.js"]
   },
 
-  // testing only
-  mincss: {
-    "assets/css/style.css": ["assets/css/style.css"]
-  },
-
-  watch: {
-    files: ["assets/**/*", "app/**/*"],
-    tasks: "lint:files concat jst",
-
-    min: {
-      files: ["assets/**/*", "app/**/*"],
-      tasks: "default"
-    }
-  },
-
-  clean: {
-    folder: "dist/"
-  }
-
 });
 
 // Run the following tasks...
-task.registerTask("default", "lint:files concat");
+task.registerTask("default", "lint:files concat min");

lib/voodoo.js

@@ -21,2 +21,4 @@ (function() {
 
+  root.version = '0.0.41';
+
   root.Voodoo = Voodoo = (function() {
@@ -27,4 +29,24 @@
         _this = this;
-      this.path_cwd = cwd;
+      if ((opts != null) && (opts._version != null)) {
+        this.version = opts._version;
+      } else {
+        this.version = root.version;
+      }
+      if ((opts != null) && (opts.base != null)) {
+        this.cwd = opts.base.substring(0, 1) === "/" ? opts.base : cwd + '/' + opts.base;
+      } else {
+        this.cwd = cwd;
+      }
+      console.log(cwd);
       this.needle_dir = __dirname + '/' + 'needles';
+      if ((opts != null) && (opts.force != null)) {
+        this.force = opts.force;
+      } else {
+        this.force = false;
+      }
+      if ((opts != null) && (opts.config != null)) {
+        this.config = opts.config;
+      } else {
+        this.config = __dirname + '/../config.js';
+      }
       tasks = fs.readdirSync(this.needle_dir).filter(function(task) {
@@ -37,6 +59,6 @@ path = __dirname + "/needles/" + task;
       grunt.cli({
-        base: this.path_cwd,
-        config: __dirname + "/../config.js",
+        base: this.cwd,
+        config: this.config,
         tasks: tasks,
-        force: opts.force
+        force: this.force
       });
@@ -56,12 +78,7 @@ }
 
-  root.getVersion = function() {
-    return JSON.parse(fs.readFileSync(path.join(__dirname, '..', 'package.json'))).version;
+  root.cli = function() {
+    p.version(root.version).option('-b, --base <path>', 'working directory for your site (where `assets` folder is in )').option('-v, --verbose', 'verbose output').option('-f, --force', 'a way to force your way past warnings. Want a suggestion? Don\'t use this option, fix your code').option('-c, --config', 'an optional config.js file, replacing the build in config.js').parse(process.argv);
+    return new Voodoo(process.cwd(), p);
   };
 
-  root.run = function() {
-    p.version(root.getVersion()).option('-v, --verbose', 'Verbose output').option('-f, --force', 'A way to force your way past warnings. Want a suggestion? Don\'t use this option, fix your code').parse(process.argv);
-    console.log("Voodoo CLI (" + p._version + ")");
-    return _this.voodoo = new Voodoo(process.cwd(), p);
-  };
-
 }).call(this);

package.json

 {
   "name": "voodoo",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "website checker/optimizer/cleaner",
@@ -21,7 +21,4 @@ "repository": {
   },
-  "devDependencies": {
-    "mocha": "0.3.3",
-    "should": "0.3.2"
-  },
   "dependencies": {
+    "coffee-script": "1.2.0",
     "ready.js": "1.3.6",
@@ -33,2 +30,6 @@ "jslint": ">= 0.0.1",
   },
+  "devDependencies": {
+    "mocha": "0.3.3",
+    "should": "0.3.2"
+  },
   "scripts": {
@@ -39,4 +40,3 @@ "test": "make test"
     "node": ">=0.5.0"
-  },
-  "devDependencies": {}
+  }
 }

README.md

 
-        .-.'  '.-.
+            .-.'  '.-.
            __  \\//  __
@@ -22,1 +22,17 @@ '_ `\\||//` _'
 Build system for our sites. When invoked, it performs so called 'needles', which contain a series of tasks such as link checking, javascript checking, css minification, ...
+
+[![Build Status](https://secure.travis-ci.org/proximitybbdo/voodoo.png)](http://travis-ci.org/proximitybbdo/voodoo)
+
+Install
+-------
+`npm install -g voodoo`
+
+Usage
+-----
+Inside your website directory, just execute `voodoo` without params to perform the basic tasks, as predefined for our framework (see `config.js` inside the repo)
+
+You can also use these parameters:
+      -b, --base <path>   working directory for your site (where `assets` folder is in )
+      -v, --verbose       verbose output
+      -f, --force         a way to force your way past warnings. Want a suggestion? Don't use this option, fix your code
+      -c, --config        an optional config.js file, replacing the build in config.js

New alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Fixed alerts

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Improved metrics

Number of package files

45

12.5%

Number of lines in readme file

38

72.73%

Number of low supply chain risk alerts

1

-66.67%

Worsened metrics

Total package byte prevSize

369719

-21.73%

Dependency count

6

20%

Dev dependency count

2

Infinity%

Lines of code

693

-63.02%

Number of medium supply chain risk alerts

1

Infinity%

Dependency changes

• + Added

  coffee-script@1.2.0

• + Added

  coffee-script@1.2.0
  (transitive)