Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump the development group across 1 directory with 6 updates #195

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 1, 2024

Bumps the development group with 5 updates in the / directory:

Package From To
@vitest/coverage-istanbul 1.4.0 1.6.0
esbuild 0.20.2 0.21.4
eslint-plugin-promise 6.1.1 6.2.0
rimraf 5.0.5 5.0.7
vitest-when 0.3.1 0.4.0

Updates @vitest/coverage-istanbul from 1.4.0 to 1.6.0

Release notes

Sourced from @​vitest/coverage-istanbul's releases.

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits

Updates esbuild from 0.20.2 to 0.21.4

Release notes

Sourced from esbuild's releases.

v0.21.4

  • Update support for import assertions and import attributes in node (#3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]
    
    example.mjs:1:40:
      1 │ import json from "esbuild/package.json" assert { type: "json" }
        │                                         ~~~~~~
        ╵                                         with
    

    Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
    async function test() {
      outer: for await (const x of [Promise.resolve([0, 1])]) {
        for (const y of x) if (y) break outer
        throw 'fail'
      }
    }
    // Old output (with --target=es6)
    function test() {
    return __async(this, null, function* () {
    outer: try {
    for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
    const x = temp.value;
    for (const y of x) if (y) break outer;
    throw "fail";
    }
    } catch (temp) {
    error = [temp];
    } finally {
    try {
    more && (temp = iter.return) && (yield temp.call(iter));
    } finally {
    if (error)
    throw error[0];
    }
    }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.4

  • Update support for import assertions and import attributes in node (#3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]
    
    example.mjs:1:40:
      1 │ import json from "esbuild/package.json" assert { type: "json" }
        │                                         ~~~~~~
        ╵                                         with
    

    Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
    async function test() {
      outer: for await (const x of [Promise.resolve([0, 1])]) {
        for (const y of x) if (y) break outer
        throw 'fail'
      }
    }
    // Old output (with --target=es6)
    function test() {
    return __async(this, null, function* () {
    outer: try {
    for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
    const x = temp.value;
    for (const y of x) if (y) break outer;
    throw "fail";
    }
    } catch (temp) {
    error = [temp];
    } finally {
    try {
    more && (temp = iter.return) && (yield temp.call(iter));
    } finally {
    if (error)
    throw error[0];
    }

... (truncated)

Commits

Updates eslint-plugin-promise from 6.1.1 to 6.2.0

Release notes

Sourced from eslint-plugin-promise's releases.

v6.2.0

6.2.0 (2024-05-27)

Bug Fixes

  • no-callback-in-promise: false positives when the exception is an argument (#446) (5e4546d)

Features

  • Resolve getAncestors and getScope calls in eslint v9 (#466) (c0c716b)
Commits
  • 5e4546d fix(no-callback-in-promise): false positives when the exception is an argumen...
  • c0c716b feat: Resolve getAncestors and getScope calls in eslint v9 (#466)
  • 7d33c30 chore: add pkg.funding (#468)
  • ce9ae7f chore(deps-dev): bump @​babel/traverse from 7.19.1 to 7.24.1 (#453)
  • 62af490 chore(deps): bump actions/checkout from 3 to 4 (#461)
  • 19b21b4 chore(deps): bump codecov/codecov-action from 3 to 4 (#459)
  • 8c74b9b chore(deps): bump actions/setup-node from 3 to 4 (#460)
  • bf75e4d chore(deps): bump cycjimmy/semantic-release-action from 3 to 4 (#462)
  • bbcfcbf chore: add tests for Node 20 (#440)
  • 0b50079 chore: remove styfle/cancel-workflow-action usage (#439)
  • Additional commits viewable in compare view

Updates rimraf from 5.0.5 to 5.0.7

Commits

Updates vitest from 1.4.0 to 1.6.0

Release notes

Sourced from vitest's releases.

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits
  • 6b29f3d chore: release v1.6.0
  • f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
  • 21e58bd feat(browser): allow injecting scripts (#5656)
  • 30f728b feat: custom "snapshotEnvironment" option (#5449)
  • 2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
  • c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
  • bdce0a2 feat: support standalone mode (#5565)
  • 40c299f fix: don't panic on empty files in node_modules
  • c9e68ce fix: hash the name of the file when caching (#5654)
  • f5faf42 fix: call resolveId('vitest') after buildStart (#5646)
  • Additional commits viewable in compare view

Updates vitest-when from 0.3.1 to 0.4.0

Commits

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 commands and options

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

… updates

Bumps the development group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `1.4.0` | `1.6.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.20.2` | `0.21.4` |
| [eslint-plugin-promise](https://github.com/eslint-community/eslint-plugin-promise) | `6.1.1` | `6.2.0` |
| [rimraf](https://github.com/isaacs/rimraf) | `5.0.5` | `5.0.7` |
| [vitest-when](https://github.com/mcous/vitest-when) | `0.3.1` | `0.4.0` |



Updates `@vitest/coverage-istanbul` from 1.4.0 to 1.6.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/coverage-istanbul)

Updates `esbuild` from 0.20.2 to 0.21.4
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.20.2...v0.21.4)

Updates `eslint-plugin-promise` from 6.1.1 to 6.2.0
- [Release notes](https://github.com/eslint-community/eslint-plugin-promise/releases)
- [Changelog](https://github.com/eslint-community/eslint-plugin-promise/blob/main/CHANGELOG.md)
- [Commits](eslint-community/eslint-plugin-promise@v6.1.1...v6.2.0)

Updates `rimraf` from 5.0.5 to 5.0.7
- [Changelog](https://github.com/isaacs/rimraf/blob/main/CHANGELOG.md)
- [Commits](isaacs/rimraf@v5.0.5...v5.0.7)

Updates `vitest` from 1.4.0 to 1.6.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.6.0/packages/vitest)

Updates `vitest-when` from 0.3.1 to 0.4.0
- [Commits](mcous/vitest-when@v0.3.1...v0.4.0)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-istanbul"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: eslint-plugin-promise
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: rimraf
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: vitest-when
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 1, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 1, 2024

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Jun 1, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/development-e8f6024a75 branch June 1, 2024 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants