Ruby Gem and Node Package for comprehensive Generation 1-7 Pokedex data, including 809 Pokémon, uses JSON schemas to verify the data
Bumps [mocha](https://github.com/mochajs/mocha) from 6.2.3 to 8.2.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/releases">mocha's releases</a>.</em></p> <blockquote> <h2>v8.2.1</h2> <h1>8.2.1 / 2020-11-02</h1> <p>Fixed stuff.</p> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4489">#4489</a>: Fix problematic handling of otherwise-unhandled <code>Promise</code> rejections and erroneous "<code>done()</code> called twice" errors (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4496">#4496</a>: Avoid <code>MaxListenersExceededWarning</code> in watch mode (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <p>Also thanks to <a href="https://github.com/akeating"><strong>@akeating</strong></a> for a documentation fix!</p> <h2>v8.2.0</h2> <h1>8.2.0 / 2020-10-16</h1> <p>The major feature added in v8.2.0 is addition of support for <a href="https://mochajs.org/#global-fixtures"><em>global fixtures</em></a>.</p> <p>While Mocha has always had the ability to run setup and teardown via a hook (e.g., a <code>before()</code> at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are <em>incompatible</em> with this strategy; e.g., a top-level <code>before()</code> would only run for the file in which it was defined.</p> <p>With <a href="https://mochajs.org/#global-fixtures">global fixtures</a>, Mocha can now perform user-defined setup and teardown <em>regardless</em> of mode, and these fixtures are guaranteed to run <em>once and only once</em>. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do <em>not</em> share context with your test files (but they do share context with each other).</p> <p>Here's a short example of usage:</p> <pre lang="js"><code>// fixtures.js <p>// can be async or not exports.mochaGlobalSetup = async function() { this.server = await startSomeServer({port: process.env.TEST_PORT}); console.log(<code>server running on port ${this.server.port}</code>); };</p> <p>exports.mochaGlobalTeardown = async function() { // the context (<code>this</code>) is shared, but not with the test files await this.server.stop(); console.log(<code>server on port ${this.server.port} stopped</code>); };</p> <p>// this file can contain root hook plugins as well! // exports.mochaHooks = { ... } </code></pre></p> <p>Fixtures are loaded with <code>--require</code>, e.g., <code>mocha --require fixtures.js</code>.</p> <p>For detailed information, please see the <a href="https://mochajs.org/#global-fixtures">documentation</a> and this handy-dandy <a href="https://mochajs.org/#test-fixture-decision-tree-wizard-thing">flowchart</a> to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).</p> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4308">#4308</a>: Support run-once <a href="https://mochajs.org/#global-fixtures">global setup & teardown fixtures</a> (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4442">#4442</a>: Multi-part extensions (e.g., <code>test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/jordanstephens"><strong>@jordanstephens</strong></a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/blob/master/CHANGELOG.md">mocha's changelog</a>.</em></p> <blockquote> <h1>8.2.1 / 2020-11-02</h1> <p>Fixed stuff.</p> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4489">#4489</a>: Fix problematic handling of otherwise-unhandled <code>Promise</code> rejections and erroneous "<code>done()</code> called twice" errors (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4496">#4496</a>: Avoid <code>MaxListenersExceededWarning</code> in watch mode (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <p>Also thanks to <a href="https://github.com/akeating"><strong>@akeating</strong></a> for a documentation fix!</p> <h1>8.2.0 / 2020-10-16</h1> <p>The major feature added in v8.2.0 is addition of support for <a href="https://mochajs.org/#global-fixtures"><em>global fixtures</em></a>.</p> <p>While Mocha has always had the ability to run setup and teardown via a hook (e.g., a <code>before()</code> at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are <em>incompatible</em> with this strategy; e.g., a top-level <code>before()</code> would only run for the file in which it was defined.</p> <p>With <a href="https://mochajs.org/#global-fixtures">global fixtures</a>, Mocha can now perform user-defined setup and teardown <em>regardless</em> of mode, and these fixtures are guaranteed to run <em>once and only once</em>. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do <em>not</em> share context with your test files (but they do share context with each other).</p> <p>Here's a short example of usage:</p> <pre lang="js"><code>// fixtures.js <p>// can be async or not exports.mochaGlobalSetup = async function() { this.server = await startSomeServer({port: process.env.TEST_PORT}); console.log(<code>server running on port ${this.server.port}</code>); };</p> <p>exports.mochaGlobalTeardown = async function() { // the context (<code>this</code>) is shared, but not with the test files await this.server.stop(); console.log(<code>server on port ${this.server.port} stopped</code>); };</p> <p>// this file can contain root hook plugins as well! // exports.mochaHooks = { ... } </code></pre></p> <p>Fixtures are loaded with <code>--require</code>, e.g., <code>mocha --require fixtures.js</code>.</p> <p>For detailed information, please see the <a href="https://mochajs.org/#global-fixtures">documentation</a> and this handy-dandy <a href="https://mochajs.org/#test-fixture-decision-tree-wizard-thing">flowchart</a> to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).</p> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4308">#4308</a>: Support run-once <a href="https://mochajs.org/#global-fixtures">global setup & teardown fixtures</a> (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4442">#4442</a>: Multi-part extensions (e.g., <code>test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/jordanstephens"><strong>@jordanstephens</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4472">#4472</a>: Leading dots (e.g., <code>.js</code>, <code>.test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4434">#4434</a>: Output of <code>json</code> reporter now contains <code>speed</code> ("fast"/"medium"/"slow") property (<a href="https://github.com/wwhurin"><strong>@wwhurin</strong></a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mochajs/mocha/commit/185cada8149c4dcac1896769c2b7732e9dbe971f"><code>185cada</code></a> Release v8.2.1</li> <li><a href="https://github.com/mochajs/mocha/commit/bddc079a50861622b0d51d6d22c730535be85afc"><code>bddc079</code></a> update CHANGELOG for v8.2.1</li> <li><a href="https://github.com/mochajs/mocha/commit/d2e0e83881dcb9dc1be621a12eaef8e6689e0391"><code>d2e0e83</code></a> ensure eslint runs properly on PRs</li> <li><a href="https://github.com/mochajs/mocha/commit/27cae393f85957d9cd11cdb1f520c7ac2a1e82ce"><code>27cae39</code></a> properly dispose Mocha instance in watch mode; closes <a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4495">#4495</a></li> <li><a href="https://github.com/mochajs/mocha/commit/5c004a96b8bc6da1f77a88d634bcd359dcaeee4a"><code>5c004a9</code></a> do not run CI on closed PRs</li> <li><a href="https://github.com/mochajs/mocha/commit/8318dff017996b015edc4d43e4640972d6a97497"><code>8318dff</code></a> update deps for some vuln which is not applicable to mocha</li> <li><a href="https://github.com/mochajs/mocha/commit/c3ced395c441a50eb144c48f4446b3a51f7a8fe7"><code>c3ced39</code></a> delegate to Node on non-Mocha unhandled rejections (<a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4489">#4489</a>)</li> <li><a href="https://github.com/mochajs/mocha/commit/fac181bb730a960c5b289e38018e4d753b662efc"><code>fac181b</code></a> Correct global fixtures release version</li> <li><a href="https://github.com/mochajs/mocha/commit/7e490aa13e8ed25c78e77faa6fed0337e948b619"><code>7e490aa</code></a> Change assert module's deprecated methods in testing files (<a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4435">#4435</a>)</li> <li><a href="https://github.com/mochajs/mocha/commit/01651120467b1c5f324e8c7a77c902bef3de07b6"><code>0165112</code></a> add node.js v15 to build matrix</li> <li>Additional commits viewable in <a href="https://github.com/mochajs/mocha/compare/v6.2.3...v8.2.1">compare view</a></li> </ul> </details> <br /> [](https://dependabot.com/compatibility-score/?dependency-name=mocha&package-manager=npm_and_yarn&previous-version=6.2.3&new-version=8.2.1) 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`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <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](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details>
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by dependabot-preview[bot] and has received 1 comments.