co-use - npm Package Compare versions

Comparing version 0.1.0 to 1.0.0

changelog.md

@@ -6,1 +6,11 @@ # Changelog
 * Initial release
+
+## 1.0.0
+
+* Tests run in harmony mode
+* co-use tests use generators
+* `npm run build` command
+* Do not run jshint on built tests
+* Build loads newest co and creates tests files for co tests
+* Build creates README.md
+* Build for co v4.6.0

package.json

 {
   "name": "co-use",
-  "version": "0.1.0",
+  "version": "1.0.0",
   "description": "co using your choice of promise implementation",
@@ -19,4 +19,7 @@ "main": "./lib/",
   "devDependencies": {
-    "co": "^4.6.0",
     "bluebird": "^2.10.0",
+    "npm-web-api": "^0.1.1",
+    "fs-extra-promise": "^0.2.1",
+    "mz": "^1.0.2",
+    "lodash": "^3.10.1",
     "mocha": "^2.3.2",
@@ -36,2 +39,3 @@ "chai": "^3.2.0",
   "scripts": {
+    "build": "make build",
     "test": "make test",
@@ -38,0 +42,0 @@ "cover": "make cover"

README.md

@@ -47,14 +47,13 @@ # co-use.js
 
-So this module is made by loading `co` and wrapping the code to add the `.use()` method. I will endeavour to update this module when new versions of co are released. The version of `co` used is noted in a comment at the top of [./lib/index.js](https://github.com/overlookmotel/co-use/blob/master/lib/index.js)
+So this module is made by loading `co` and wrapping the code to add the `.use()` method. I will endeavour to update this module when new versions of co are released. The version of `co` currently used is `v4.6.0`.
 
-If you wish to build `co-use` with a more recent version of `co`, do the following:
+If you wish to build `co-use` with the most recent version of `co`, do the following:
 
 1. Fork `co-use` from Github
-2. Update the version of co in `package.json` to the latest
-3. Go to the directory of the fork
-4. Run the following code:
+2. Go to the directory of the fork
+3. Run the following code:
 
 ```
-npm update  # loads latest version of co
-node ./bin/build.js
+npm install
+npm run build
 ```
@@ -61,0 +60,0 @@

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

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

12587

increased by1.32%

Number of low quality alerts

1

decreased by-50%

Worsened metrics

Dev dependency count

10

increased by42.86%

Number of lines in readme file

82

decreased by-1.2%

No dependency changes