@leverege/build-tools 2.39.0-beta.2 → 2.39.0-beta.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "2.39.0-beta.2",
+  "version": "2.39.0-beta.3",
   "description": "A collection of build / support tools for Leverege developers",
   "main": "index.js",
   "repository": {
@@ -8,14 +8,8 @@
     "url": "git+ssh://git@bitbucket.org/leverege/build-tools.git"
   },
   "scripts": {
-    "build": "npm run compile",
     "clean": "rm -rf lib",
-    "compile": "npm run clean && npm run compile_server && npm run compile_web",
-    "compile_server": "NODE_ENV=server babel -d lib/server src/",
-    "compile_web": "NODE_ENV=web babel -d lib/web src/",
     "lint": "find ./src -name \\*.\\*js | xargs npx eslint --report-unused-disable-directives",
-    "xprepublintOnly": "npm run lint && npm run build",
-    "xprepublishOnly": "npm run compile",
     "test": "echo \"Error: no test specified\" && exit 1"
   },
   "bin": {

package/src/refresh-npm-token.mjs

@@ -66,8 +66,7 @@ const refreshTokenOptions = [ // Use refreshTokenOptions to tie into the Usage s
 const sections = [
   {
     header : 'Leverege NPM Token Refresher',
-    content : `{green
-This tool helps you retrieve an npmrc file stored in a secret within a GCP
+    content : `{green This tool helps you retrieve an npmrc file stored in a secret within a GCP
 Secret Manager. It enables NPM administrators to manage a single NPM token
 for use by a development team. The tool checks the age of your local ~/.npmrc
 file, and if it exceeds the specified --npmrc-age setting, it will fetch the
@@ -76,14 +75,48 @@ secret, overwriting the existing ~/.npmrc file.
 This tool may be invoked directly from the command line, or from scripts in
 the build-tools repository. For example, helmup will invoke this command for
 refreshing the token and to provide an audit log to slack when deployments
-are made.}
-`
+are made.}`
   },
   { header : 'Options',
     optionList : refreshTokenOptions,
   },
+  {
+    header : 'Secret Manager Secrets (required)',
+    content : [
+      '{bold REFRESH_NPM_NPMRC}    {green full npmrc file with a valid token}',
+      `{green     ;;;;
+    ; lines that start with semi-colons are comments
+    ; run "npm help 7 config" for documentation of the various options
+    ;
+    ; expires on 11/20/23
+    //registry.npmjs.org/:_authToken=<a valid npm token goes here>
+    loglevel=error
+    progress=true
+
+    init.license=SEE LICENSE IN LICENSE.md
+    init.private=true
+
+  There may be times when a token is expired, lost or a new developer needs
+  to seed their ~/.npmrc file for the first time. Help a brother out and let
+  them know to run this command to fetch the current npmrc file:
+
+    gcloud secrets versions access latest \\
+         --secret=NPM_DEVELOPER_NPMRC     \\
+         --project=leverege-registry > ~/.npmrc
+
+  Note, ^^that command will need a different --project name for non-leverege
+  developers.
+      }`,
+      `{bold REFRESH_NPM_SLACK_CONFIG} {green resembles the following JSON struct
+  \\{
+    "url" : "https://hooks.slack.com/services/T....H/Bx....1/44....gLr7",
+    "channel" : "#some-devops-channel"
+  \\} }`
+    ],
+  },
   { header : 'Environment Variables (optional)',
-    content : '{bold REFRESH_NPM_PROJECT}  {green may be used in lieu of --project}',
+    content : `{bold REFRESH_NPM_PROJECT}  {green may be used in lieu of --project
+    }`,
   },
 ]