I've implemented a partial fix. SPARQLgraph now makes it very difficult for you to create a circular graph. Further improvements are possible, but let's see whether this one gets us what we need.

Bumps npm-check-updates from 2.14.2 to 11.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #99.

Bumps npm-check-updates from 2.14.2 to 11.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Bumps mathjax from 2.7.9 to 3.1.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mathjax/MathJax/releases">mathjax's releases</a>.</em></p> <blockquote> <h2>MathJax v3.1.4</h2> <p>This is a hot fix release to fix two problems with the recent 3.1.3 version. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.4">release notes</a> for details.</p> <h2>MathJax 3.1.3</h2> <p>This is a bug fix release that resolves more than 70 issues, and updates a number of modules on which MathJax relies. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.3">release notes</a> for details.</p> <h2>MathJax v3.1.2</h2> <p>Hot fix to correct regression introduced in v3.1.1 that caused control sequences followed by spaces to not be recognized.</p> <h2>MathJax v3.1.1</h2> <p>This is a bug fix release to address issues that arose from the recent 3.1.0 release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a> for details.</p> <h2>MathJax v3.1.0</h2> <p>This is a feature release that includes a number of API improvements, new extensions, and updates to the assistive tools, as described in the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a>.</p> <h2>MathJax v3.0.5</h2> <p>This is a hot fix release to resolve an important issue with horizontal stretchy characters (e.g., <code>\overline</code> and <code>\overrightarrow</code>) in CommonHTML output that was introduced in the recent version 3.0.4 release.</p> <h2>MathJax v3.0.4</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.4">release notes</a> for details.</p> <p>Note that version 3.0.2 and 3.0.3 had problems with their <code>npm</code> deployment (some files where missing from the package), so were removed. This is the next actual version after 3.0.1</p> <h2>MathJax v3.0.1</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.1">release notes</a> for details.</p> <h2>MathJax v3.0.0</h2> <p>After over two years of development, the MathJax team is pleased to announce the official release of MathJax 3.0.0!</p> <p>This version is a complete rewrite of MathJax from the ground up using modern programming techniques, including Typescript, ES6 modules, Promises, and more.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/whats-new-3.0.html">What's New in v3.0</a> section of the documentation for details about the new version 3.0.0.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/v2.html">Upgrading from v2</a> instructions for details about what is and isn't in version 3, and how to upgrade your site from version 2. Note in particular that there is a <a href="https://mathjax.github.io/MathJax-demos-web/convert-configuration/convert-configuration.html">configuration converter</a> that can help you move from version 2 to version 3.</p> <p>See the <a href="http://docs.mathjax.org/">documentation</a> for details about how to use MathJax.</p> <p>See the <a href="https://github.com/mathjax/MathJax-src">MathJax Source Repository</a> for the source code for versions 3.</p> <p>There are two repositories that contain examples of using MathJax, one for web pages, and one for use with node on a server:</p> <ul> <li><a href="https://github.com/mathjax/MathJax-demos-web#mathjax-demos-web">MathJax Web Examples</a></li> <li><a href="https://github.com/mathjax/MathJax-demos-node#mathjax-demos-node">MathJax Node Examples</a></li> </ul> <p>Please use the <a href="https://github.com/mathjax/MathJax/issues">MathJax Issue Tracker</a> to report problems in version 3 of MathJax.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mathjax/MathJax/commit/be11806df1ae075508e33500c990497062ef3c5a"><code>be11806</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/e0575afdda9d94b9ba1d9045ebbce15b4476c465"><code>e0575af</code></a> Update to version 3.1.4</li> <li><a href="https://github.com/mathjax/MathJax/commit/af2bacdb2a38245a4a68c84bf7a5fb2e6da35426"><code>af2bacd</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/de316b931638887c26525aad4ac55acaca7093cd"><code>de316b9</code></a> Update package.json and files to v3.1.3</li> <li><a href="https://github.com/mathjax/MathJax/commit/ec5c85494ad89f5e60c727c0b5c8534a966be09d"><code>ec5c854</code></a> Merge branch 'update-shields' into develop</li> <li><a href="https://github.com/mathjax/MathJax/commit/10160614b6b5844f231c91423533fbddd28d55cb"><code>1016061</code></a> Merge branch 'update-shields'</li> <li><a href="https://github.com/mathjax/MathJax/commit/117409ac26dbabf70b9915dc49d9623e0000fde5"><code>117409a</code></a> Add shields for rank and downloads</li> <li><a href="https://github.com/mathjax/MathJax/commit/1335230503dddfeb0e07687308a55795d9c005e8"><code>1335230</code></a> Update issue templates</li> <li><a href="https://github.com/mathjax/MathJax/commit/c8292351190ce249f7143f224dbe7a190c8228fe"><code>c829235</code></a> Update to version 3.1.2</li> <li><a href="https://github.com/mathjax/MathJax/commit/3ee0287eb1d6101aef8ec5af1e06042a656a91fc"><code>3ee0287</code></a> Update to version 3.1.1</li> <li>Additional commits viewable in <a href="https://github.com/mathjax/MathJax/compare/2.7.9...3.1.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #98.

Bumps mathjax from 2.7.9 to 3.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mathjax/MathJax/releases">mathjax's releases</a>.</em></p> <blockquote> <h2>MathJax v3.2.0</h2> <p>This is a feature release that includes a new lazy-typesetting extension, nine new TeX extensions, a port of the v2 MML3 extension, new Hindi support in the expression explorer, along with several other improvements, and a number of bug fixes. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.2.0">release notes</a> for details.</p> <h2>MathJax v3.1.4</h2> <p>This is a hot fix release to fix two problems with the recent 3.1.3 version. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.4">release notes</a> for details.</p> <h2>MathJax 3.1.3</h2> <p>This is a bug fix release that resolves more than 70 issues, and updates a number of modules on which MathJax relies. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.3">release notes</a> for details.</p> <h2>MathJax v3.1.2</h2> <p>Hot fix to correct regression introduced in v3.1.1 that caused control sequences followed by spaces to not be recognized.</p> <h2>MathJax v3.1.1</h2> <p>This is a bug fix release to address issues that arose from the recent 3.1.0 release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a> for details.</p> <h2>MathJax v3.1.0</h2> <p>This is a feature release that includes a number of API improvements, new extensions, and updates to the assistive tools, as described in the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a>.</p> <h2>MathJax v3.0.5</h2> <p>This is a hot fix release to resolve an important issue with horizontal stretchy characters (e.g., <code>\overline</code> and <code>\overrightarrow</code>) in CommonHTML output that was introduced in the recent version 3.0.4 release.</p> <h2>MathJax v3.0.4</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.4">release notes</a> for details.</p> <p>Note that version 3.0.2 and 3.0.3 had problems with their <code>npm</code> deployment (some files where missing from the package), so were removed. This is the next actual version after 3.0.1</p> <h2>MathJax v3.0.1</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.1">release notes</a> for details.</p> <h2>MathJax v3.0.0</h2> <p>After over two years of development, the MathJax team is pleased to announce the official release of MathJax 3.0.0!</p> <p>This version is a complete rewrite of MathJax from the ground up using modern programming techniques, including Typescript, ES6 modules, Promises, and more.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/whats-new-3.0.html">What's New in v3.0</a> section of the documentation for details about the new version 3.0.0.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/v2.html">Upgrading from v2</a> instructions for details about what is and isn't in version 3, and how to upgrade your site from version 2. Note in particular that there is a <a href="https://mathjax.github.io/MathJax-demos-web/convert-configuration/convert-configuration.html">configuration converter</a> that can help you move from version 2 to version 3.</p> <p>See the <a href="http://docs.mathjax.org/">documentation</a> for details about how to use MathJax.</p> <p>See the <a href="https://github.com/mathjax/MathJax-src">MathJax Source Repository</a> for the source code for versions 3.</p> <p>There are two repositories that contain examples of using MathJax, one for web pages, and one for use with node on a server:</p> <ul> <li><a href="https://github.com/mathjax/MathJax-demos-web#mathjax-demos-web">MathJax Web Examples</a></li> <li><a href="https://github.com/mathjax/MathJax-demos-node#mathjax-demos-node">MathJax Node Examples</a></li> </ul> <p>Please use the <a href="https://github.com/mathjax/MathJax/issues">MathJax Issue Tracker</a> to report problems in version 3 of MathJax.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mathjax/MathJax/commit/7146ffa47956e7dae05739cfe905d8aaf1e4780a"><code>7146ffa</code></a> Release version 3.2.0</li> <li><a href="https://github.com/mathjax/MathJax/commit/05b057160d5210bb1c41510a7b0ed2e1b8a5c2b9"><code>05b0571</code></a> Update to version 3.2.0</li> <li><a href="https://github.com/mathjax/MathJax/commit/be11806df1ae075508e33500c990497062ef3c5a"><code>be11806</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/e0575afdda9d94b9ba1d9045ebbce15b4476c465"><code>e0575af</code></a> Update to version 3.1.4</li> <li><a href="https://github.com/mathjax/MathJax/commit/af2bacdb2a38245a4a68c84bf7a5fb2e6da35426"><code>af2bacd</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/de316b931638887c26525aad4ac55acaca7093cd"><code>de316b9</code></a> Update package.json and files to v3.1.3</li> <li><a href="https://github.com/mathjax/MathJax/commit/ec5c85494ad89f5e60c727c0b5c8534a966be09d"><code>ec5c854</code></a> Merge branch 'update-shields' into develop</li> <li><a href="https://github.com/mathjax/MathJax/commit/10160614b6b5844f231c91423533fbddd28d55cb"><code>1016061</code></a> Merge branch 'update-shields'</li> <li><a href="https://github.com/mathjax/MathJax/commit/117409ac26dbabf70b9915dc49d9623e0000fde5"><code>117409a</code></a> Add shields for rank and downloads</li> <li><a href="https://github.com/mathjax/MathJax/commit/1335230503dddfeb0e07687308a55795d9c005e8"><code>1335230</code></a> Update issue templates</li> <li>Additional commits viewable in <a href="https://github.com/mathjax/MathJax/compare/2.7.9...3.2.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Bumps npm-check-updates from 2.14.2 to 11.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Superseded by #35.

Bumps npm-check-updates from 2.14.2 to 11.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

Bumps npm-check-updates from 11.5.11 to 11.6.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>See full diff in <a href="https://github.com/raineorshine/npm-check-updates/compare/v11.5.11...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Superseded by #38.

Bumps npm-check-updates from 11.5.11 to 11.7.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v11.5.11...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Adds fix for GaloisInc/what4#133