Change to require Node.js 16

packages/remark-lint-blockquote-indentation/readme.md

@@ -261,7 +261,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-blockquote-indentation@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-checkbox-character-style/readme.md

@@ -312,7 +312,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-checkbox-character-style@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-checkbox-content-indent/readme.md

@@ -222,7 +222,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-checkbox-content-indent@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-code-block-style/readme.md

@@ -305,7 +305,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-code-block-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-definition-case/readme.md

@@ -195,7 +195,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-definition-case@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-definition-spacing/readme.md

@@ -198,7 +198,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-definition-spacing@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-emphasis-marker/readme.md

@@ -277,7 +277,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-emphasis-marker@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-fenced-code-flag/readme.md

@@ -313,7 +313,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-fenced-code-flag@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-fenced-code-marker/readme.md

@@ -288,7 +288,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-fenced-code-marker@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-file-extension/readme.md

@@ -237,7 +237,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-file-extension@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-final-definition/readme.md

@@ -258,7 +258,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-final-definition@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-final-newline/readme.md

@@ -180,7 +180,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-final-newline@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-first-heading-level/readme.md

@@ -262,7 +262,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-first-heading-level@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-hard-break-spaces/readme.md

@@ -199,7 +199,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-hard-break-spaces@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-heading-increment/readme.md

@@ -256,7 +256,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-heading-increment@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-heading-style/readme.md

@@ -283,7 +283,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-heading-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-linebreak-style/readme.md

@@ -265,7 +265,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-linebreak-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-link-title-style/readme.md

@@ -358,7 +358,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-link-title-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-list-item-bullet-indent/readme.md

@@ -199,7 +199,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-list-item-bullet-indent@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-list-item-content-indent/readme.md

@@ -254,7 +254,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-list-item-content-indent@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-list-item-indent/readme.md

@@ -510,7 +510,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-list-item-indent@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-list-item-spacing/readme.md

@@ -277,7 +277,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-list-item-spacing@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-maximum-heading-length/readme.md

@@ -210,7 +210,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-maximum-heading-length@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-maximum-line-length/readme.md

@@ -343,7 +343,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-maximum-line-length@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-blockquote-without-marker/readme.md

@@ -252,7 +252,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-blockquote-without-marker@5`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-consecutive-blank-lines/readme.md

@@ -421,7 +421,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-consecutive-blank-lines@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-duplicate-defined-urls/readme.md

@@ -174,7 +174,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-duplicate-defined-urls@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-duplicate-definitions/readme.md

@@ -199,7 +199,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-duplicate-definitions@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-duplicate-headings-in-section/readme.md

@@ -233,7 +233,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-duplicate-headings-in-section@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-duplicate-headings/readme.md

@@ -206,7 +206,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-duplicate-headings@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-emphasis-as-heading/readme.md

@@ -188,7 +188,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-emphasis-as-heading@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-empty-url/readme.md

@@ -183,7 +183,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-empty-url@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-file-name-articles/readme.md

@@ -172,7 +172,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-file-name-articles@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-file-name-consecutive-dashes/readme.md

@@ -156,7 +156,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-file-name-consecutive-dashes@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-file-name-irregular-characters/readme.md

@@ -203,7 +203,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-file-name-irregular-characters@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-file-name-mixed-case/readme.md

@@ -163,7 +163,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-file-name-mixed-case@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-file-name-outer-dashes/readme.md

@@ -164,7 +164,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-file-name-outer-dashes@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-heading-content-indent/readme.md

@@ -212,7 +212,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-heading-content-indent@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-heading-indent/readme.md

@@ -208,7 +208,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-heading-indent@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-heading-like-paragraph/readme.md

@@ -173,7 +173,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-heading-like-paragraph@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-heading-punctuation/readme.md

@@ -240,7 +240,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-heading-punctuation@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-html/readme.md

@@ -194,7 +194,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-html@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-literal-urls/readme.md

@@ -201,7 +201,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-literal-urls@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-missing-blank-lines/readme.md

@@ -337,7 +337,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-missing-blank-lines@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-multiple-toplevel-headings/readme.md

@@ -259,7 +259,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-multiple-toplevel-headings@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-paragraph-content-indent/readme.md

@@ -201,7 +201,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-paragraph-content-indent@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-reference-like-url/readme.md

@@ -195,7 +195,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-reference-like-url@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-shell-dollars/readme.md

@@ -207,7 +207,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-shell-dollars@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-shortcut-reference-image/readme.md

@@ -182,7 +182,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-shortcut-reference-image@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-shortcut-reference-link/readme.md

@@ -182,7 +182,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-shortcut-reference-link@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-table-indentation/readme.md

@@ -231,7 +231,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-table-indentation@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-tabs/readme.md

@@ -216,7 +216,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-tabs@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-undefined-references/readme.md

@@ -321,7 +321,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-undefined-references@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-unneeded-full-reference-image/readme.md

@@ -209,7 +209,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-unneeded-full-reference-image@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-unneeded-full-reference-link/readme.md

@@ -209,7 +209,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-unneeded-full-reference-link@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-no-unused-definitions/readme.md

@@ -199,7 +199,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-no-unused-definitions@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-ordered-list-marker-style/readme.md

@@ -255,7 +255,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-ordered-list-marker-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-ordered-list-marker-value/readme.md

@@ -409,7 +409,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-ordered-list-marker-value@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-rule-style/readme.md

@@ -240,7 +240,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-rule-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-strikethrough-marker/readme.md

@@ -279,7 +279,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-strikethrough-marker@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-strong-marker/readme.md

@@ -277,7 +277,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-strong-marker@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-table-cell-padding/readme.md

@@ -687,7 +687,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-table-cell-padding@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-table-pipe-alignment/readme.md

@@ -419,7 +419,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-table-pipe-alignment@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-table-pipes/readme.md

@@ -280,7 +280,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-table-pipes@4`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint-unordered-list-marker-style/readme.md

@@ -269,7 +269,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint-unordered-list-marker-style@3`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-lint/readme.md

@@ -141,7 +141,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-lint@9`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-preset-lint-consistent/readme.md

@@ -145,7 +145,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-preset-lint-consistent@5`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-preset-lint-markdown-style-guide/readme.md

@@ -264,7 +264,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-preset-lint-markdown-style-guide@5`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/remark-preset-lint-recommended/readme.md

@@ -145,7 +145,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `remark-preset-lint-recommended@6`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

packages/unified-lint-rule/readme.md

@@ -164,7 +164,7 @@ When we cut a new major release, we drop support for unmaintained versions of
 Node.
 This means we try to keep the current release line,
 `unified-lint-rule@2`,
-compatible with Node.js 12.
+compatible with Node.js 16.
 
 ## Contribute
 

readme.md

@@ -595,10 +595,13 @@ Notable examples that deeply integrate with it are
 
 ## Compatibility
 
-Projects maintained by the unified collective are compatible with all maintained
+Projects maintained by the unified collective are compatible with maintained
 versions of Node.js.
-As of now, that is Node.js 12.20+, 14.14+, and 16.0+.
-Our projects sometimes work with older versions, but this is not guaranteed.
+
+When we cut a new major release, we drop support for unmaintained versions of
+Node.
+This means we try to keep the current release line, `remark-lint@9`, compatible
+with Node.js 16.
 
 ## Security
 

script/pipeline-package.js

@@ -1457,7 +1457,7 @@ function generateReadmeTail(state) {
         },
         {
           type: 'text',
-          value: ',\ncompatible with Node.js 12.'
+          value: ',\ncompatible with Node.js 16.'
         }
       ]
     },

tsconfig.json

@@ -9,7 +9,7 @@
     "lib": ["dom", "es2022"],
     "module": "node16",
     "strict": true,
-    "target": "es2020"
+    "target": "es2022"
   },
   "exclude": ["**/coverage/", "**/node_modules/"],
   "include": ["**/*.js"]