chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates

[dependabot]

Bumps the dev-dependencies group with 7 updates in the /vscode directory:

Package	From	To
@typescript-eslint/eslint-plugin	7.12.0	8.4.0
@typescript-eslint/parser	7.12.0	8.4.0
@vscode/vsce	2.27.0	3.1.0
esbuild	0.21.5	0.23.1
eslint-plugin-prettier	5.1.3	5.2.1
gts	5.3.0	5.3.1
ovsx	0.9.1	0.9.2

Updates @typescript-eslint/eslint-plugin from 7.12.0 to 8.4.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.4.0

8.4.0 (2024-09-02)

🚀 Features

• typescript-estree: make withoutProjectParserOptions generic (#9877)

❤️ Thank You

• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v8.3.0

8.3.0 (2024-08-26)

🚀 Features

• eslint-plugin: [no-deprecation] add rule (#9783)
• typescript-estree: replace globby w/ fast-glob (#9518)
• typescript-estree: reload project service once when file config isn't found (#9853)

🩹 Fixes

• ast-spec: use Expression in argument of ThrowStatement (#9632)
• eslint-plugin: [no-unnecessary-template-expression] add missing parentheses in autofix (#8673)
• eslint-plugin: [no-unnecessary-type-parameters] check mapped alias type arguments (#9741)
• utils: add missing TSSatisfiesExpression in RuleListenerBaseSelectors (#9832)
• utils: add TSDeclareFunction to functionTypeTypes (#9788)

❤️ Thank You

• Abraham Guo
• Daichi Kamiyama @​dak2
• Josh Goldberg ✨
• Kim Sang Du @​developer-bandi
• Sukka
• Vida Xie @​9romise

You can read about our versioning strategy and releases on our website.

v8.2.0

8.2.0 (2024-08-19)

🚀 Features

• eslint-plugin: add suggestion to require-await to remove async keyword (#9718)

... (truncated)

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.4.0 (2024-09-02)

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.3.0 (2024-08-26)

🚀 Features

• eslint-plugin: [no-deprecation] add rule

🩹 Fixes

• eslint-plugin: [no-unnecessary-template-expression] add missing parentheses in autofix

• eslint-plugin: [no-unnecessary-type-parameters] check mapped alias type arguments

• utils: add TSDeclareFunction to functionTypeTypes

• ast-spec: use Expression in argument of ThrowStatement

❤️ Thank You

• Abraham Guo
• Daichi Kamiyama
• Josh Goldberg ✨
• Kim Sang Du
• Sukka
• Vida Xie

You can read about our versioning strategy and releases on our website.

8.2.0 (2024-08-19)

🚀 Features

• eslint-plugin: add suggestion to require-await to remove async keyword

🩹 Fixes

• eslint-plugin: [use-unknown-in-catch-callback-variable] flag second argument of .then

• eslint-plugin: [no-unnecessary-type-assertion] conflict with TS for variables used before assignment

... (truncated)

Commits

• 3920c93 chore(release): publish 8.4.0
• 2ad3404 chore: enable unicorn/prefer-export-from and `@typescript-eslint/consistent...
• 46f27e6 docs: added note on async generator support in require-await (#9795)
• e5d1ac4 docs: add dedicated TypeOrValueSpecifier docs page (#9875)
• 5fd4251 docs: fill in most remaining rule option descriptions (#9868)
• 2421575 docs: add global variable rule disabling FAQ for ESLint (#9865)
• ef2eab1 chore(release): publish 8.3.0
• fd55358 chore: enable sonarjs/no-duplicated-branches (#9821)
• 9f70ed1 fix(ast-spec): use Expression in argument of ThrowStatement (#9632)
• 7160687 chore: enable unicorn/no-lonely-if (#9830)
• Additional commits viewable in compare view

Updates @typescript-eslint/parser from 7.12.0 to 8.4.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.4.0

8.4.0 (2024-09-02)

🚀 Features

• typescript-estree: make withoutProjectParserOptions generic (#9877)

❤️ Thank You

• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v8.3.0

8.3.0 (2024-08-26)

🚀 Features

• eslint-plugin: [no-deprecation] add rule (#9783)
• typescript-estree: replace globby w/ fast-glob (#9518)
• typescript-estree: reload project service once when file config isn't found (#9853)

🩹 Fixes

• ast-spec: use Expression in argument of ThrowStatement (#9632)
• eslint-plugin: [no-unnecessary-template-expression] add missing parentheses in autofix (#8673)
• eslint-plugin: [no-unnecessary-type-parameters] check mapped alias type arguments (#9741)
• utils: add missing TSSatisfiesExpression in RuleListenerBaseSelectors (#9832)
• utils: add TSDeclareFunction to functionTypeTypes (#9788)

❤️ Thank You

• Abraham Guo
• Daichi Kamiyama @​dak2
• Josh Goldberg ✨
• Kim Sang Du @​developer-bandi
• Sukka
• Vida Xie @​9romise

You can read about our versioning strategy and releases on our website.

v8.2.0

8.2.0 (2024-08-19)

🚀 Features

• eslint-plugin: add suggestion to require-await to remove async keyword (#9718)

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.4.0 (2024-09-02)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.3.0 (2024-08-26)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.2.0 (2024-08-19)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.1.0 (2024-08-12)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.0.1 (2024-08-05)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.0.0 (2024-07-31)

🚀 Features

• parser: always enable comment, loc, range, tokens

• typescript-estree: stabilize EXPERIMENTAL_useProjectService as projectService

❤️ Thank You

• Abraham Guo
• Alfred Ringstad
• auvred
• Brad Zacher
• Christopher Aubut
• Collin Bachman
• James Henry
• Josh Goldberg

... (truncated)

Commits

• 3920c93 chore(release): publish 8.4.0
• 2ad3404 chore: enable unicorn/prefer-export-from and `@typescript-eslint/consistent...
• ef2eab1 chore(release): publish 8.3.0
• 9612d81 chore: enable eslint-plugin-perfectionist on parser package (#9845)
• 7440e14 chore(release): publish 8.2.0
• 382e87b chore: enable unicorn/prefer-node-protocol (#9742)
• 243fb5f chore: enable prefer-template (#9544)
• 3d78392 chore(release): publish 8.1.0
• a26e3c7 chore: enable prefer-regexp-test (#9658)
• e05c2e5 chore(release): publish 8.0.1
• Additional commits viewable in compare view

Updates @vscode/vsce from 2.27.0 to 3.1.0

Release notes

Sourced from @​vscode/vsce's releases.

v3.1.0

Changes:

Feature Requests:

• #1044: Enable verifying the signed package

Others:

• #1050: Fix unused-files-patterns check and add tests
• #1046: Fix typo in option hint
• #1045: add verify-signature command. Fixes #1044
• #1037: Fix punycode deprecation warning
• #1040: Allow packaging extension without a publisher

This list of changes was auto generated.

v3.0.1-4

Changes:

• #1050: Fix unused-files-patterns check and add tests

This list of changes was auto generated.

v3.0.1-3

Changes:

• #1046: Fix typo in option hint

This list of changes was auto generated.

v3.0.1-2

Changes:

Feature Requests:

• #1044: Enable verifying the signed package

... (truncated)

Commits

• ba66818 Merge pull request #1050 from microsoft/benibenj/narrow-smelt
• 0e9cb5a More logging
• 65f32a0 More error logging
• a2e01db Merge branch 'main' into benibenj/narrow-smelt
• 134eaa6 fix unused-files-patterns check and add tests
• 3090717 Merge pull request #1046 from mlasson/patch-1
• a583bab Fix typo in option hint
• 164eebd add verify-signature command. Fixes #1044 (#1045)
• e646982 Merge pull request #1037 from mark-wiemer/users/markwiemer/930-punycode
• f7c7b44 Merge branch 'main' into users/markwiemer/930-punycode
• Additional commits viewable in compare view

Updates esbuild from 0.21.5 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

v0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

... (truncated)

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• 9d50680 publish 0.23.0 to npm
• Additional commits viewable in compare view

Updates eslint-plugin-prettier from 5.1.3 to 5.2.1

Release notes

Sourced from eslint-plugin-prettier's releases.

v5.2.1

Patch Changes

• #668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

Changelog

Sourced from eslint-plugin-prettier's changelog.

5.2.1

Patch Changes

• #668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

5.2.0

Minor Changes

• #652 f170011 Thanks @​Logicer16! - feat: support parsing html via @html-eslint/parser natively

Commits

• 51324d9 chore: fix CHANGELOG.md formatting issue
• 24288c7 chore: release eslint-plugin-prettier (#669)
• ac036cc build(deps): Bump synckit from 0.8.6 to 0.9.1 (#668)
• a1e6f4a build(deps): Bump braces from 3.0.2 to 3.0.3 (#665)
• de9751c build(deps): Bump pnpm/action-setup from 2 to 4 in the actions group (#661)
• 02c21a5 chore: release eslint-plugin-prettier (#653)
• f170011 feat: support parsing html via @html-eslint/parser natively (#652)
• See full diff in compare view

Updates gts from 5.3.0 to 5.3.1

Release notes

Sourced from gts's releases.

v5.3.1

5.3.1 (2024-04-10)

Bug Fixes

• deps: replace dependency eslint-plugin-node with eslint-plugin-n (#865) (efbe3a8)
• deps: update dependency eslint to v8.57.0 (#833) (0c0a45c)
• deps: update dependency prettier to v3.2.5 (#846) (7e60e38)

Performance Improvements

• Supercharge Performance & Efficiency: Leveraging Promise.all for Resource-Friendly Tasks 🚤 (#838) (7424fe1)

Changelog

Sourced from gts's changelog.

5.3.1 (2024-04-10)

Bug Fixes

• deps: replace dependency eslint-plugin-node with eslint-plugin-n (#865) (efbe3a8)
• deps: update dependency eslint to v8.57.0 (#833) (0c0a45c)
• deps: update dependency prettier to v3.2.5 (#846) (7e60e38)

Performance Improvements

• Supercharge Performance & Efficiency: Leveraging Promise.all for Resource-Friendly Tasks 🚤 (#838) (7424fe1)

Commits

• db44cce chore(main): release 5.3.1 (#862)
• 3c054cd chore(deps): update dependency @​types/node to v20.12.7 (#872)
• eefd53a chore(deps): lock file maintenance (#874)
• c0db7ab chore(deps): update dependency @​types/node to v20.12.4 (#871)
• 9cd12a8 chore(deps): lock file maintenance (#842)
• 39c78a4 chore(deps): update dependency @​types/node to v20.12.3 (#870)
• 5c87d95 chore(deps): update dependency @​types/node to v20.12.2 (#869)
• efbe3a8 fix(deps): replace dependency eslint-plugin-node with eslint-plugin-n (#865)
• 0bd8195 build: test on node 18 (#866)
• 7424fe1 perf: Supercharge Performance & Efficiency: Leveraging Promise.all for Reso...
• Additional commits viewable in compare view

Updates ovsx from 0.9.1 to 0.9.2

Changelog

Sourced from ovsx's changelog.

v0.9.2 (July 2024)

Bug Fixes

• Remove default universal for get operation (#944)

Dependencies

• Upgrade braces from 3.0.2 to 3.0.3 (#953)

---

Commits

• 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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.