fix(docs): link foreground-scripts w/ loglevel

Since loglevel is the first place people usually look to find out why their scripts have no output when they are in the background, this will help point them to the config that addresses that situation. PR-URL: #3360 Credit: @wraithgar Close: #3360 Reviewed-by: @isaacs
npm · Jun 3, 2021 · ca28221 · ca28221
1 parent aafe235
commit ca28221
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 0 deletions.
diff --git a/docs/content/using-npm/config.md b/docs/content/using-npm/config.md
@@ -776,6 +776,8 @@ What level of logs to report. On failure, *all* logs are written to
 Any logs of a higher level than the setting are shown. The default is
 "notice".
 
+See also the `foreground-scripts` config.
+
 #### `logs-max`
 
 * Default: 10

diff --git a/lib/utils/config/definitions.js b/lib/utils/config/definitions.js
@@ -1128,6 +1128,8 @@ define('loglevel', {
 
     Any logs of a higher level than the setting are shown. The default is
     "notice".
+
+    See also the \`foreground-scripts\` config.
   `,
 })
 

diff --git a/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs b/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs
@@ -655,6 +655,8 @@ What level of logs to report. On failure, *all* logs are written to
 Any logs of a higher level than the setting are shown. The default is
 "notice".
 
+See also the \`foreground-scripts\` config.
+
 #### \`logs-max\`
 
 * Default: 10