envkey - npm Package Compare versions

Comparing version 1.2.6 to 1.2.7

loader.js

@@ -185,3 +185,3 @@ var dotenv = require("dotenv"),
       filePath = path.join(__dirname, "ext", ["envkey-fetch", ENVKEY_FETCH_VERSION, platformPart, archPart].join("_"), ("envkey-fetch" + ext)),
-      execArgs = [key, (isDev ? "--cache" : ""), "--client-name", "envkey-node", "--client-version", "1.2.6"]
+      execArgs = [key, (isDev ? "--cache" : ""), "--client-name", "envkey-node", "--client-version", "1.2.7"]
 
@@ -216,4 +216,9 @@ if (cb){
     } catch (e){
-      console.error(e.stderr.toString())
-      throw(e.stderr.toString())
+      if (e.stderr){
+        console.error(e.stderr.toString())
+        throw(e.stderr.toString())
+      } else {
+        console.error(e.stack)
+        throw(e)
+      }
     }
@@ -220,0 +225,0 @@ }

package.json

 {
   "name": "envkey",
-  "version": "1.2.6",
+  "version": "1.2.7",
   "description": "EnvKey secures and simplifies application secrets and config.",
@@ -5,0 +5,0 @@ "repository": "https://github.com/envkey/envkey-js",

README.md

@@ -134,2 +134,9 @@ # envkey npm package
 
+## x509 error / ca-certificates
+
+On a stripped down OS like Alpine Linux, you may get an `x509: certificate signed by unknown authority` error when `envkey-node` attempts to load your config. [envkey-fetch](https://github.com/envkey/envkey-fetch) attempts to handle this by including its own set of trusted CAs via [gocertifi](https://github.com/certifi/gocertifi), but if you're getting this error anyway, you can fix it by ensuring that the `ca-certificates` dependency is installed. On Alpine you'll want to run:
+```
+apk add --no-cache ca-certificates
+```
+
 ## Further Reading
@@ -136,0 +143,0 @@

No alert changes

Improved metrics

Total package byte prevSize

80906959

Lines of code

335

increased by1.52%

Number of lines in readme file

155

increased by4.73%

No dependency changes