expect - npm Package Compare versions

Comparing version 0.1.1 to 1.0.0

package.json

 {
   "name": "expect",
-  "version": "0.1.1",
+  "version": "1.0.0",
   "description": "Write better assertions",
-  "main": "expect.js",
+  "main": "modules/expect.js",
   "dependencies": {},
@@ -11,3 +11,3 @@ "devDependencies": {
   "scripts": {
-    "test": "mocha spec"
+    "test": "mocha \"modules/**/__tests__/**/*-test.js\""
   },
@@ -24,8 +24,8 @@ "keywords": [
     "type": "git",
-    "url": "git://github.com/mjijackson/expect.git"
+    "url": "git://github.com/mjackson/expect.git"
   },
   "bugs": {
-    "url": "https://github.com/mjijackson/expect/issues"
+    "url": "https://github.com/mjackson/expect/issues"
   },
-  "homepage": "https://github.com/mjijackson/expect"
+  "homepage": "https://github.com/mjackson/expect"
 }

README.md

@@ -1,6 +0,8 @@
-[expect](https://github.com/mjijackson/expect) is a thin wrapper around node's [assert](http://nodejs.org/api/assert.html) module that lets you write better assertions.
+[![build status](https://secure.travis-ci.org/mjackson/expect.png)](http://travis-ci.org/mjackson/expect)
 
+[expect](https://github.com/mjackson/expect) is a thin wrapper around node's [assert](http://nodejs.org/api/assert.html) module that lets you write better assertions.
+
 When you use expect, you write assertions similarly to how you would say them, e.g. "I expect this value to be equal to 3" or "I expect this array to contain 3". When you write assertions in this way, you don't need to remember the order of actual and expected arguments to functions like `assert.equal`, which helps you write better tests.
 
-### API
+### Usage
 
@@ -85,4 +87,21 @@ #### expect(object).toBe(value, [message])
 
+### Installation
+
+Using [npm](https://www.npmjs.org/):
+
+    $ npm install expect
+
+### Issues
+
+Please file issues on the [issue tracker on GitHub](https://github.com/machjs/mach/issues).
+
+### Tests
+
+To run the tests in node:
+
+    $ npm install
+    $ npm test
+
 ### License
 
-MIT
+[MIT](http://opensource.org/licenses/MIT)

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

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

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

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

11521

increased by52.43%

Number of package files

11

increased by175%

Lines of code

191

increased by107.61%

Number of low quality alerts

0

decreased by-100%

Number of lines in readme file

107

increased by21.59%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes