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

[dependabot]

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

Package	From	To
@typescript-eslint/eslint-plugin	7.12.0	7.16.0
@typescript-eslint/parser	7.12.0	7.16.0
@vscode/vsce	2.27.0	2.30.0
esbuild	0.21.5	0.23.0
gts	5.3.0	5.3.1

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

Release notes

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

v7.16.0

7.16.0 (2024-07-08)

🚀 Features

• ast-spec: add parent property to AccessorProperty node types (#9487)
• eslint-plugin: [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule (#8903)
• eslint-plugin: add support for nested namespaces to unsafe-member-access (#9478)
• eslint-plugin: [no-floating-promises] add checkThenables option (#9263)
• rule-tester: stricter rule test validations (#9086)

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0 (#9497)
• eslint-plugin: [no-floating-promises] add suggestions to tests from #9263 checkThenables (#9515, #9263)
• eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled (#9492)
• utils: context.parserPath may be undefined (#9486)
• website: react key error on internal pages of website (#9506)

❤️ Thank You

• Abraham Guo
• auvred @​auvred
• Josh Goldberg ✨
• Juan Sanchez @​JSanchezIO
• Vinccool96
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

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

v7.15.0

7.15.0 (2024-07-01)

🚀 Features

• eslint-plugin: [array-type] detect Readonly<string[]> case (#8752)
• eslint-plugin: back-port new rules around empty object types from v8 (#9443)

🩹 Fixes

• disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config (#9459)
• eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any (#9254)
• eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any (#9304)
• utils: clean outdated RuleTester export (#9322)

❤️ Thank You

... (truncated)

Changelog

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

7.16.0 (2024-07-08)

🚀 Features

• rule-tester: stricter rule test validations

• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule

• eslint-plugin: add support for nested namespaces to unsafe-member-access

• eslint-plugin: [no-floating-promises] add checkThenables option

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0

• eslint-plugin: [no-floating-promises] add suggestions to tests from #9263 checkThenables

• website: react key error on internal pages of website

• eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled

❤️ Thank You

• Abraham Guo
• auvred
• Josh Goldberg ✨
• Juan Sanchez
• Vinccool96
• YeonJuan
• Yukihiro Hasegawa

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

7.15.0 (2024-07-01)

🚀 Features

• eslint-plugin: [array-type] detect Readonly<string[]> case

• eslint-plugin: back-port new rules around empty object types from v8

🩹 Fixes

• disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config

... (truncated)

Commits

• e803c50 chore(release): publish 7.16.0
• 7b13dae fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `a...
• 3c6290d fix(eslint-plugin): [no-floating-promises] add suggestions to tests from #9...
• 63d17dd feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)
• d685948 feat(eslint-plugin): add support for nested namespaces to unsafe-member-acces...
• 451e738 feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new r...
• 88dd828 feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
• a1a9b09 chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eva...
• d364160 docs: [class-methods-use-this] fix typo (#9494)
• 7e2b77d feat(rule-tester): stricter rule test validations (#9086)
• Additional commits viewable in compare view

Updates @typescript-eslint/parser from 7.12.0 to 7.16.0

Release notes

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

v7.16.0

7.16.0 (2024-07-08)

🚀 Features

• ast-spec: add parent property to AccessorProperty node types (#9487)
• eslint-plugin: [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule (#8903)
• eslint-plugin: add support for nested namespaces to unsafe-member-access (#9478)
• eslint-plugin: [no-floating-promises] add checkThenables option (#9263)
• rule-tester: stricter rule test validations (#9086)

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0 (#9497)
• eslint-plugin: [no-floating-promises] add suggestions to tests from #9263 checkThenables (#9515, #9263)
• eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled (#9492)
• utils: context.parserPath may be undefined (#9486)
• website: react key error on internal pages of website (#9506)

❤️ Thank You

• Abraham Guo
• auvred @​auvred
• Josh Goldberg ✨
• Juan Sanchez @​JSanchezIO
• Vinccool96
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

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

v7.15.0

7.15.0 (2024-07-01)

🚀 Features

• eslint-plugin: [array-type] detect Readonly<string[]> case (#8752)
• eslint-plugin: back-port new rules around empty object types from v8 (#9443)

🩹 Fixes

• disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config (#9459)
• eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any (#9254)
• eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any (#9304)
• utils: clean outdated RuleTester export (#9322)

❤️ Thank You

... (truncated)

Changelog

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

7.16.0 (2024-07-08)

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0

• website: react key error on internal pages of website

❤️ Thank You

• Abraham Guo
• auvred
• Josh Goldberg ✨
• Juan Sanchez
• Vinccool96
• YeonJuan
• Yukihiro Hasegawa

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

7.15.0 (2024-07-01)

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.

7.14.1 (2024-06-24)

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.

7.14.0 (2024-06-24)

🚀 Features

• support TypeScript 5.5

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

... (truncated)

Commits

• e803c50 chore(release): publish 7.16.0
• 2865d31 chore(release): publish 7.15.0
• b4fe94f chore(release): publish 7.14.1
• dfc4469 chore(release): publish 7.14.0
• 1212a8f chore(release): publish 7.13.1
• 8a178ed chore(release): publish 7.13.0
• c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
• See full diff in compare view

Updates @vscode/vsce from 2.27.0 to 2.30.0

Release notes

Sourced from @​vscode/vsce's releases.

v2.30.0

Changes:

Feature Requests:

• #1009: Azure - create a custom chained token credential to place the AzureCLICredential prior to the ManagedIdentityCredential

Others:

• #1011: Validate publisher on package
• #1013: Print packaged files/folders

This list of changes was auto generated.

v2.29.1-2

Changes:

• #1011: Validate publisher on package

This list of changes was auto generated.

v2.29.1-1

Changes:

• #1013: Print packaged files/folders

This list of changes was auto generated.

v2.29.1-0

Changes:

Feature Requests:

• #1009: Azure - create a custom chained token credential to place the AzureCLICredential prior to the ManagedIdentityCredential

This list of changes was auto generated.

... (truncated)

Commits

• 7dc3477 Merge pull request #1011 from microsoft/benibenj/legitimate-impala
• f06c324 Merge pull request #1013 from microsoft/benibenj/psychiatric-orangutan
• 53d517e Print packaged files
• 67f7374 validate publisher on package
• b6ccc05 Azure - create a custom chained token credential to place the AzureCLICredent...
• 33daacd fix #1006 (#1007)
• dba04c7 Merge pull request #1003 from microsoft/benibenj/mass-cardinal
• 03d0e03 fix #997
• 9f69378 fix generate-manifest (#1002)
• 1151559 Bump braces from 3.0.2 to 3.0.3 (#1001)
• Additional commits viewable in compare view

Updates esbuild from 0.21.5 to 0.23.0

Release notes

Sourced from esbuild's releases.

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:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012

... (truncated)

Changelog

Sourced from esbuild's changelog.

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)

  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:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008

... (truncated)

Commits

• 9d50680 publish 0.23.0 to npm
• ac7fd04 Revert "fix #1874: node defaults to --packages=external" (#3820)
• 626ac2c fix #3818: preserve collapsed jsx whitespace
• 7c2eb2e hashbang syntax is part of es2023
• 80c6e6e publish 0.22.0 to npm
• 196dcad fix #1874: node defaults to --packages=external
• 3f57db8 release notes for #3539
• 91663db Provide API to create a custom esbuild CLI with plugins (#3539)
• e01c0e0 also mention #3665 in release notes
• 65711b3 release notes for #3674
• Additional commits viewable 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

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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[dependabot]

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