co-fs-extra - npm Package Compare versions

Comparing version 0.1.0 to 1.0.0

index.js

@@ -11,8 +11,10 @@
 
-thunkify(fs, methods);
-module.exports = fs;
 
+for (var key in fs) {
+  exports[key] = fs[key];
+}
+
 // .exists is still messed
 
-fs.exists = function (path) {
+exports.exists = function (path) {
   return function (done) {
@@ -27,4 +29,6 @@ fs.stat(path, function(err, res){
 
-fs.createReadStream = function () {
+exports.createReadStream = function () {
   return stream(fs.createReadStream.apply(null, arguments));
 };
+
+thunkify(module.exports, methods);

package.json

 {
   "name": "co-fs-extra",
-  "version": "0.1.0",
+  "version": "1.0.0",
   "description": "fs-extra for 'co'",
@@ -5,0 +5,0 @@ "author": {

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

Fixed alerts

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

3204

increased by6.13%

Number of package files

9

increased by12.5%

Lines of code

87

increased by2.35%

Number of low quality alerts

1

decreased by-50%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes