jasmine-core - npm Package Compare versions

Comparing version 2.0.1 to 2.0.4

CONTRIBUTING.md

@@ -112,3 +112,3 @@ # Developing for Jasmine Core
 1. Ensure all specs are green in browser *and* node
-1. Ensure JSHint is green with `grunt jsHint`
+1. Ensure JSHint is green with `grunt jshint`
 1. Build `jasmine.js` with `grunt buildDistribution` and run all specs again - this ensures that your changes self-test well
@@ -115,0 +115,0 @@

lib/console/console.js

@@ -157,2 +157,3 @@ /*
         printNewline();
+        print(indent(failedExpectation.message, 2));
         print(indent(failedExpectation.stack, 2));
@@ -159,0 +160,0 @@ }

lib/jasmine-core.js

 module.exports = require("./jasmine-core/jasmine.js");
 module.exports.boot = require('./jasmine-core/node_boot.js');
+
+module.exports.files = (function() {
+  var path = require('path'),
+      fs = require('fs');
+
+  var rootPath = path.join(__dirname, "jasmine-core"),
+      bootFiles = ['boot.js'],
+      nodeBootFiles = ['node_boot.js'],
+      cssFiles = [],
+      jsFiles = [],
+      jsFilesToSkip = ['jasmine.js'].concat(bootFiles, nodeBootFiles);
+
+  fs.readdirSync(rootPath).forEach(function(file) {
+    if(fs.statSync(path.join(rootPath, file)).isFile()) {
+      switch(path.extname(file)) {
+        case '.css':
+          cssFiles.push(file);
+          break;
+        case '.js':
+          if (jsFilesToSkip.indexOf(file) < 0) {
+            jsFiles.push(file);
+          }
+          break;
+      }
+    }
+  });
+
+  return {
+    path: rootPath,
+    bootDir: rootPath,
+    bootFiles: bootFiles,
+    nodeBootFiles: nodeBootFiles,
+    cssFiles: cssFiles,
+    jsFiles: ['jasmine.js'].concat(jsFiles),
+    imagesDir: path.join(__dirname, '../images')
+  };
+}());

lib/jasmine-core/node_boot.js

@@ -31,57 +31,6 @@ /*
 
-  var jasmineInterface = {
-    describe: function(description, specDefinitions) {
-      return env.describe(description, specDefinitions);
-    },
+  var jasmineInterface = jasmineRequire.interface(jasmine, env);
 
-    xdescribe: function(description, specDefinitions) {
-      return env.xdescribe(description, specDefinitions);
-    },
-
-    it: function(desc, func) {
-      return env.it(desc, func);
-    },
-
-    xit: function(desc, func) {
-      return env.xit(desc, func);
-    },
-
-    beforeEach: function(beforeEachFunction) {
-      return env.beforeEach(beforeEachFunction);
-    },
-
-    afterEach: function(afterEachFunction) {
-      return env.afterEach(afterEachFunction);
-    },
-
-    expect: function(actual) {
-      return env.expect(actual);
-    },
-
-    spyOn: function(obj, methodName) {
-      return env.spyOn(obj, methodName);
-    },
-
-    jsApiReporter: new jasmine.JsApiReporter({
-      timer: new jasmine.Timer()
-    }),
-
-
-    jasmine: jasmine
-  };
-
   extend(global, jasmineInterface);
 
-  jasmine.addCustomEqualityTester = function(tester) {
-    env.addCustomEqualityTester(tester);
-  };
-
-  jasmine.addMatchers = function(matchers) {
-    return env.addMatchers(matchers);
-  };
-
-  jasmine.clock = function() {
-    return env.clock;
-  };
-
   function extend(destination, source) {
@@ -92,4 +41,3 @@ for (var property in source) destination[property] = source[property];
 
-
   return jasmine;
 };

package.json

 {
   "name": "jasmine-core",
   "license": "MIT",
-  "version": "2.0.1",
+  "version": "2.0.4",
   "repository": {
@@ -6,0 +6,0 @@ "type": "git",

RELEASE.md

@@ -24,10 +24,2 @@ # How to work on a Jasmine Release
 
-### Update the Github Pages (as needed)
-
-___Note: This is going to change right after 2.0___
-
-Github pages have to exist in a branch called `gh-pages` in order for their app to serve them. This repo adds that branch as a submodule under the `pages` directory. This is a bit of a hack, but it allows us to work with the pages and the source at the same time and with one set of rake tasks.
-
-If you want to submit changes to this repo and aren't a Pivotal Labs employee, you can fork and work in the `gh-pages` branch. You won't be able to edit the pages in the submodule off of master.
-
 ## Release
@@ -59,2 +51,7 @@
 
+### Release the NPM
+
+1. `npm adduser` to save your credentials locally
+1. `npm publish .` to publish what's in `package.json`
+
 ### Finally
@@ -61,0 +58,0 @@

New alerts

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

Filesystem access

Supply chain risk

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

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1991081

16.46%

Number of package files

272

23.08%

Lines of code

3448

18%

Worsened metrics

Number of low supply chain risk alerts

1

Infinity%

Number of medium supply chain risk alerts

1

Infinity%

No dependency changes