application-config - npm Package Compare versions

Comparing version 0.2.2 to 1.0.0

index.js

@@ -36,3 +36,13 @@ var fs = require('fs')
 
-    fs.writeFile(self.filePath, JSON.stringify(data, null, 2), cb)
+    var tempFilePath =
+      self.filePath + '-' +
+      Math.random().toString().substr(2) +
+      Date.now().toString() +
+      path.extname(self.filePath)
+
+    fs.writeFile(tempFilePath, JSON.stringify(data, null, 2), function (err) {
+      if (err) { return cb(err) }
+
+      fs.rename(tempFilePath, self.filePath, cb)
+    })
   })
@@ -39,0 +49,0 @@ }

package.json

 {
   "name": "application-config",
-  "version": "0.2.2",
+  "version": "1.0.0",
   "license": "MIT",
@@ -17,3 +17,3 @@ "author": "Linus Unnebäck <[e-mail]>",
     "mocha": "^2.1.0",
-    "standard": "^5.0.1-0"
+    "standard": "^7.1.2"
   },
@@ -20,0 +20,0 @@ "scripts": {

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

5830

increased by4.67%

Lines of code

106

increased by8.16%

Number of low quality alerts

0

decreased by-100%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes