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 all group with 5 updates #156

Merged
merged 1 commit into from
Dec 26, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 25, 2023

Bumps the all group with 5 updates:

Package From To
@vitest/coverage-v8 1.0.4 1.1.0
@vitest/ui 1.0.4 1.1.0
esbuild 0.19.9 0.19.10
eslint-plugin-vitest 0.3.18 0.3.20
vitest 1.0.4 1.1.0

Updates @vitest/coverage-v8 from 1.0.4 to 1.1.0

Release notes

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

v1.1.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub
Commits

Updates @vitest/ui from 1.0.4 to 1.1.0

Release notes

Sourced from @​vitest/ui's releases.

v1.1.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • 9497f48 chore: release v1.1.0
  • f43fdd8 fix(ui): show file item when search filter matches only test cases (#4736)
  • 7191103 fix(ui): fix coverage iframe url for html report preview (#4717)
  • c4e865b chore(deps): update dependency @​iconify-json/logos to ^1.1.41 (#4769)
  • e0dde6a fix(ui): escape html for console log view (#4724)
  • See full diff in compare view

Updates esbuild from 0.19.9 to 0.19.10

Release notes

Sourced from esbuild's releases.

v0.19.10

  • Fix glob imports in TypeScript files (#3319)

    This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

  • Fix require() glob imports with bundling disabled (#3546)

    Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

  • Fix a panic when transforming optional chaining with define (#3551, #3554)

    This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

    // Original code
    console.log(process?.env.SHELL)
    // Old output (with --define:process.env={})
    /* panic: Internal error (while parsing "<stdin>") */
    // New output (with --define:process.env={})
    var define_process_env_default = {};
    console.log(define_process_env_default.SHELL);

    This fix was contributed by @​hi-ogawa.

  • Work around a bug in node's CommonJS export name detector (#3544)

    The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

    When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

    // confuseNode.js
    exports.confuseNode = function(exports) {
      // If this local is called "exports", node incorrectly
      // thinks this file has an export called "notAnExport".
      exports.notAnExport = function() {
      };
    };

    You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

    $ node -e 'import("./confuseNode.js").then(console.log)'
    [Module: null prototype] {
      confuseNode: [Function (anonymous)],
      default: { confuseNode: [Function (anonymous)] },

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.19.10

  • Fix glob imports in TypeScript files (#3319)

    This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

  • Fix require() glob imports with bundling disabled (#3546)

    Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

  • Fix a panic when transforming optional chaining with define (#3551, #3554)

    This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

    // Original code
    console.log(process?.env.SHELL)
    // Old output (with --define:process.env={})
    /* panic: Internal error (while parsing "<stdin>") */
    // New output (with --define:process.env={})
    var define_process_env_default = {};
    console.log(define_process_env_default.SHELL);

    This fix was contributed by @​hi-ogawa.

  • Work around a bug in node's CommonJS export name detector (#3544)

    The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

    When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

    // confuseNode.js
    exports.confuseNode = function(exports) {
      // If this local is called "exports", node incorrectly
      // thinks this file has an export called "notAnExport".
      exports.notAnExport = function() {
      };
    };

    You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

    $ node -e 'import("./confuseNode.js").then(console.log)'
    [Module: null prototype] {
      confuseNode: [Function (anonymous)],

... (truncated)

Commits
  • 55e1127 publish 0.19.10 to npm
  • d968af2 fix #3511: @__NO_SIDE_EFFECTS__ with templates
  • 00c4ebe fix #3546: don't transform require glob imports
  • e1b7050 fix #3319: missing symbol usage in glob transform
  • 461ca73 add the @esbuild/aix-ppc64 package for ibm aix (#3550)
  • 190ca99 truncate a long url in a comment
  • 6c41900 add Safari compat data for arbitrary module namespace names (#3520)
  • f38cbe6 fix #3552: calling stop() now clears go timeouts
  • 7a225ff make a few code edits from some random github bot
  • aa46b2c fix some build script comments
  • Additional commits viewable in compare view

Updates eslint-plugin-vitest from 0.3.18 to 0.3.20

Release notes

Sourced from eslint-plugin-vitest's releases.

v0.3.20

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.19...v0.3.20

v0.3.19

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.18...v0.3.19

Commits
  • 426fc92 chore: release v0.3.20
  • 488d6dc chore(tests): remove unused tests
  • b00417d chore(expect-expect): fix expect on skipped tests
  • 423f0a7 chore: release v0.3.19
  • 21dccf3 fix(false positive): stop false positive (#340)
  • 71422ec chore(changes): updated changes (#337)
  • 0076439 feat(deprecate): deprecate done callback (#335)
  • dc190c9 chore(prefer-to-be): don't make prefer to be a recomended rule (#332)
  • See full diff in compare view

Updates vitest from 1.0.4 to 1.1.0

Release notes

Sourced from vitest's releases.

v1.1.0

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • 9497f48 chore: release v1.1.0
  • e975b57 types: use satisfies for defaults (#4738)
  • f859efc feat: add --exclude CLI flag (#4279)
  • 4d55a02 feat: add --no-isolate flag to improve performance, add documentation about p...
  • fd5d7e6 feat: add --no-file-parallelism, --maxWorkers, --minWorkers flags (#4705)
  • 67d93ed feat: add --workspace option, fix root resolution in workspaces (#4773)
  • 8dabef8 fix(vitest): pass down CLI options to override workspace configs (#4774)
  • 5a71eb3 fix: correctly reset provided values (#4775)
  • 9cc3668 fix(types): defineWorkspace fix intellisense and report type errors (#4743)
  • 9c552b6 chore(deps): update dependency @​types/prompts to ^2.4.9 (#4720)
  • See full diff in compare view

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

Bumps the all group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `1.0.4` | `1.1.0` |
| [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) | `1.0.4` | `1.1.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.19.9` | `0.19.10` |
| [eslint-plugin-vitest](https://github.com/veritem/eslint-plugin-vitest) | `0.3.18` | `0.3.20` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.0.4` | `1.1.0` |


Updates `@vitest/coverage-v8` from 1.0.4 to 1.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.1.0/packages/coverage-v8)

Updates `@vitest/ui` from 1.0.4 to 1.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.1.0/packages/ui)

Updates `esbuild` from 0.19.9 to 0.19.10
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.19.9...v0.19.10)

Updates `eslint-plugin-vitest` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/veritem/eslint-plugin-vitest/releases)
- [Commits](vitest-dev/eslint-plugin-vitest@v0.3.18...v0.3.20)

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

---
updated-dependencies:
- dependency-name: "@vitest/coverage-v8"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: "@vitest/ui"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: eslint-plugin-vitest
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
...

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 Dec 25, 2023
@nihalgonsalves nihalgonsalves merged commit 3216935 into main Dec 26, 2023
1 check passed
@nihalgonsalves nihalgonsalves deleted the dependabot/npm_and_yarn/all-4e5c82cd21 branch December 26, 2023 07:41
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.

1 participant