refactor: use the ci flag force no proxy in ci/pre-publish tests.

Author: scottdurow

jest-ci.config.js

@@ -6,12 +6,13 @@
   "scripts": {
     "build": "tsc",
     "test": "jest",
-    "ci-test": "jest --runInBand --ci --config=jest-ci.config.js",
+    "ci-test": "jest --runInBand --ci",
     "unit-test": "jest unit-tests/",
     "integration-test": "jest integration-tests/",
     "browser-tests-build": "webpack --config webpack.config.js --watch",
     "start-browser": "webpack --config webpack.config.js --watch",
-    "preversion": "npm run ci-test",
+    "prepublish-test": "npm run ci-test",
+    "preversion": "npm run prepublish-test",
     "version": "npm run build",
     "postversion": "git push",
     "prepublishOnly": "npm version patch",

package.json

@@ -1,6 +1,11 @@
 module.exports = async function (globalConfig, projectConfig) {
   require("dotenv").config();
-  if (process.env["DATAVERSEIFY_USEPROXY"] === "1") {
+  // If running in CI mode, never use the proxy - otherwise, control using the DATAVERSEIFY_USEPROXY environment variable set in the .env file
+  /*
+  DATAVERSEIFY_USEPROXY=1
+  DATAVERSEIFY_PROXY=https://127.0.0.1:8888
+  */
+  if (!globalConfig.ci && process.env["DATAVERSEIFY_USEPROXY"] === "1") {
     const httpProxy = process.env["DATAVERSEIFY_PROXY"];
     console.debug("Adding proxy:" + httpProxy);
     if (!httpProxy) {