Skip to content

Commit 49a8456

Browse files
Anatoly BolshakovAlexander Smolyakov
andauthored
Added notes about disabling of Node 6 warning message (#15534)
* Added notes about disabling * Update docs/migrateNode10.md Co-authored-by: Alexander Smolyakov <[email protected]> * Updated table of content * Fixed typo Co-authored-by: Alexander Smolyakov <[email protected]>
1 parent 6ab084f commit 49a8456

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/migrateNode10.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
- [Common packages dependent on `azure-pipeline-task-lib`](#common-packages-dependent-on-azure-pipeline-task-lib)
44
- [List of known dependency issues](#list-of-known-dependency-issues)
55
- [`fs` module](#fs-module)
6+
- [How to disable warnings for Node 6 deprecation](#how-to-disable-warnings-for-node-6-deprecation)
67

78
# Upgrading Tasks to Node 10
89

@@ -111,4 +112,9 @@ The following `fs` functions all have incompatibilities. In addition, any other
111112
- fs.unlink
112113
- fs.utimes
113114
- fs.write
114-
- fs.writeFile
115+
- fs.writeFile
116+
117+
# How to disable warnings for Node 6 deprecation
118+
To avoid noise in pipeline logs - you can disable Node 6 deprecation warnings by setting up DISABLE_NODE6_DEPRECATION_WARNING agent knob in one of 2 ways:
119+
- Set up `DISABLE_NODE6_DEPRECATION_WARNING` pipeline variable as `true`
120+
- For self-hosted agents - set up environment variable `DISABLE_NODE6_DEPRECATION_WARNING` as `true`

0 commit comments

Comments
 (0)