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.

Sign up for GitHub

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

Jump to bottom

Bump the dependencies group with 14 updates #242

Closed
wants to merge 1 commit into from
Closed

Bump the dependencies group with 14 updates #242

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 12, 2024 •
edited
Loading

Bumps the dependencies group with 14 updates:

Package From To
@types/node 20.10.6 20.11.17
@types/vscode 1.85.0 1.86.0
@typescript-eslint/eslint-plugin 6.16.0 6.21.0
@typescript-eslint/parser 6.16.0 6.21.0
@vscode/test-electron 2.3.8 2.3.9
@vscode/vsce 2.22.0 2.23.0
chai 5.0.0 5.1.0
esbuild 0.19.11 0.20.0
eslint-config-standard-with-typescript 43.0.0 43.0.1
eslint-plugin-n 16.6.0 16.6.2
mocha 10.2.0 10.3.0
prettier 3.1.1 3.2.5
prettier-eslint 16.2.0 16.3.0
utility-types 3.10.0 3.11.0

Updates @types/node from 20.10.6 to 20.11.17

Commits

Updates @types/vscode from 1.85.0 to 1.86.0

Commits

Updates @typescript-eslint/eslint-plugin from 6.16.0 to 6.21.0

Release notes

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

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

  • export plugin metadata (#8331)
  • allow parserOptions.project: false (#8339)
  • eslint-plugin: add rule prefer-find (#8216)
  • typescript-estree: forbid duplicated accessibility modifiers (#8257)
  • utils: improve eslint types (#8344)

🩹 Fixes

  • ast-spec: add JSXElement type to the JSXAttribute['value'] (#8285)
  • eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression (#8265)
  • eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values (#8250)
  • eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions (#8332)
  • eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option (#8249)
  • eslint-plugin: [class-literal-property-style] allow getter when same key setter exists (#8277)
  • eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword (#8326)
  • rule-tester: fix a phantom dependency on the "semver" package (#8260)

❤️ Thank You

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

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

  • eslint-plugin: [member-ordering] allow easy reuse of the default ordering (#8248)

🩹 Fixes

  • eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result (#8283)
  • eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)
  • eslint-plugin: [no-useless-template-literals] report Infinity & NaN (#8295)
  • eslint-plugin: [prefer-readonly] disable checking accessors (#8300)

❤️ Thank You

... (truncated)

Changelog

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

6.21.0 (2024-02-05)

🚀 Features

  • export plugin metadata

  • allow parserOptions.project: false

  • eslint-plugin: add rule prefer-find

🩹 Fixes

  • eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression

  • eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values

  • eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions

  • eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option

  • eslint-plugin: [class-literal-property-style] allow getter when same key setter exists

  • eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword

❤️ Thank You

  • auvred
  • Brad Zacher
  • Kirk Waiblinger
  • Pete Gonzalez
  • YeonJuan

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

6.20.0 (2024-01-29)

🚀 Features

  • eslint-plugin: [member-ordering] allow easy reuse of the default ordering

🩹 Fixes

  • eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result

  • eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable

... (truncated)

Commits
  • 289ee88 chore(release): publish 6.21.0
  • f892a72 docs(eslint-plugin): mention alternatives in no-explicit-any (#8370)
  • aa5edf7 chore(deps): update dependency prettier to v3.2.4 (#8357)
  • 1d7447f chore(eslint-plugin): [no-invalid-void-type] fix Options typing to reflect ...
  • e2b46e0 fix(eslint-plugin): [no-unnecessary-type-assertion] provide valid fixes for a...
  • 3bbb78d feat(eslint-plugin): add rule prefer-find (#8216)
  • 9883ee2 feat: export plugin metadata (#8331)
  • 69bd501 fix(eslint-plugin): [class-literal-property-style] allow getter when same key...
  • cd5dff8 chore: bump eslint versions (#8338)
  • 8d62ee6 chore: remove unnecessary eslint-disable comments (#8336)
  • Additional commits viewable in compare view

Updates @typescript-eslint/parser from 6.16.0 to 6.21.0

Release notes

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

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

  • export plugin metadata (#8331)
  • allow parserOptions.project: false (#8339)
  • eslint-plugin: add rule prefer-find (#8216)
  • typescript-estree: forbid duplicated accessibility modifiers (#8257)
  • utils: improve eslint types (#8344)

🩹 Fixes

  • ast-spec: add JSXElement type to the JSXAttribute['value'] (#8285)
  • eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression (#8265)
  • eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values (#8250)
  • eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions (#8332)
  • eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option (#8249)
  • eslint-plugin: [class-literal-property-style] allow getter when same key setter exists (#8277)
  • eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword (#8326)
  • rule-tester: fix a phantom dependency on the "semver" package (#8260)

❤️ Thank You

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

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

  • eslint-plugin: [member-ordering] allow easy reuse of the default ordering (#8248)

🩹 Fixes

  • eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result (#8283)
  • eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)
  • eslint-plugin: [no-useless-template-literals] report Infinity & NaN (#8295)
  • eslint-plugin: [prefer-readonly] disable checking accessors (#8300)

❤️ Thank You

... (truncated)

Changelog

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

6.21.0 (2024-02-05)

🚀 Features

  • allow parserOptions.project: false

❤️ Thank You

  • auvred
  • Brad Zacher
  • Kirk Waiblinger
  • Pete Gonzalez
  • YeonJuan

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

6.20.0 (2024-01-29)

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.

6.19.1 (2024-01-22)

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.

6.19.0 (2024-01-15)

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.

6.18.1 (2024-01-08)

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.

6.18.0 (2024-01-06)

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.

6.17.0 (2024-01-01)

... (truncated)

Commits

Updates @vscode/test-electron from 2.3.8 to 2.3.9

Changelog

Sourced from @​vscode/test-electron's changelog.

2.3.9 | 2024-01-19

  • Fix archive extraction on Windows failing when run under Electron
Commits

Updates @vscode/vsce from 2.22.0 to 2.23.0

Commits

Updates chai from 5.0.0 to 5.1.0

Release notes

Sourced from chai's releases.

v5.1.0

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

Commits

Updates esbuild from 0.19.11 to 0.20.0

Release notes

Sourced from esbuild's releases.

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#3609, #3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#3341, #3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

  • The "preserve" JSX mode now preserves JSX text verbatim (#3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;

  • Allow JSX elements as JSX attribute values

    JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#3609, #3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#3341, #3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

0.19.12

  • The "preserve" JSX mode now preserves JSX text verbatim (#3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;

  • Allow JSX elements as JSX attribute values

... (truncated)

Commits

Updates eslint-config-standard-with-typescript from 43.0.0 to 43.0.1

Release notes

Sourced from eslint-config-standard-with-typescript's releases.

v43.0.1

43.0.1 (2024-1-20)

Build system / dependencies

  • rm add-to-project workflow (8d2f497)

Documentation

Changelog

Sourced from eslint-config-standard-with-typescript's changelog.

43.0.1 (2024-1-20)

Build system / dependencies

  • rm add-to-project workflow (8d2f497)

Documentation

Commits
  • a15c932 chore(release): 43.0.1 [skip ci]
  • c7782be Merge pull request #1394 from mightyiam/renovate/semantic-release-23.x
  • 5fb79c3 chore(deps): update dependency semantic-release to v23
  • d3b4d11 Merge pull request #1400 from mightyiam/renovate/node-20.x
  • 7414eba chore(deps): update dependency @​types/node to v20.11.5
  • 8470a93 Merge pull request #1397 from mightyiam/repo-transfer
  • 932ffce docs: update repository urls
  • 372e604 Merge pull request #1399 from mightyiam/project
  • 8d2f497 build: rm add-to-project workflow
  • cd71373 Merge pull request #1393 from standard/renovate/node-20.x
  • Additional commits viewable in compare view

Updates eslint-plugin-n from 16.6.0 to 16.6.2

Release notes

Sourced from eslint-plugin-n's releases.

Release 16.6.2

  • fix: no-callback-literal ignore unknown nodes (#163) (5fc2198)

Release 16.6.1

  • fix: eslint 7.0 support (#156) (2419888)
Commits

Updates mocha from 10.2.0 to 10.3.0

Release notes

Sourced from mocha's releases.

v10.3.0

This is a stable release equivalent to v10.3.0-preminor.0.

What's Changed

New Contributors

Full Changelog: mochajs/mocha@v10.2.0...v10.3.0

v10.3.0-preminor.0

A test release tagged with next on npm, to test that we can do releases at all. See #5081 for context.

What's Changed

... (truncated)

Changelog

Sourced from mocha's changelog.

10.3.0 / 2024-02-08

This is a stable release equivalent to 10.30.0-prerelease.

10.3.0-prerelease / 2024-01-18

This is a prerelease version to test our ability to release. Other than removing or updating dependencies, it contains no intended user-facing changes.

🔩 Other

@dependabot
Bump the dependencies group with 14 updates
6ad3019 
Bumps the dependencies group with 14 updates:

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.10.6` | `20.11.17` |
| [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/vscode) | `1.85.0` | `1.86.0` |
| [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `6.16.0` | `6.21.0` |
| [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `6.16.0` | `6.21.0` |
| [@vscode/test-electron](https://github.com/Microsoft/vscode-test) | `2.3.8` | `2.3.9` |
| [@vscode/vsce](https://github.com/Microsoft/vsce) | `2.22.0` | `2.23.0` |
| [chai](https://github.com/chaijs/chai) | `5.0.0` | `5.1.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.19.11` | `0.20.0` |
| [eslint-config-standard-with-typescript](https://github.com/mightyiam/eslint-config-standard-with-typescript) | `43.0.0` | `43.0.1` |
| [eslint-plugin-n](https://github.com/eslint-community/eslint-plugin-n) | `16.6.0` | `16.6.2` |
| [mocha](https://github.com/mochajs/mocha) | `10.2.0` | `10.3.0` |
| [prettier](https://github.com/prettier/prettier) | `3.1.1` | `3.2.5` |
| [prettier-eslint](https://github.com/prettier/prettier-eslint) | `16.2.0` | `16.3.0` |
| [utility-types](https://github.com/piotrwitek/utility-types) | `3.10.0` | `3.11.0` |


Updates `@types/node` from 20.10.6 to 20.11.17
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@types/vscode` from 1.85.0 to 1.86.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/vscode)

Updates `@typescript-eslint/eslint-plugin` from 6.16.0 to 6.21.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.21.0/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 6.16.0 to 6.21.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.21.0/packages/parser)

Updates `@vscode/test-electron` from 2.3.8 to 2.3.9
- [Changelog](https://github.com/microsoft/vscode-test/blob/main/CHANGELOG.md)
- [Commits](https://github.com/Microsoft/vscode-test/commits/v2.3.9)

Updates `@vscode/vsce` from 2.22.0 to 2.23.0
- [Release notes](https://github.com/Microsoft/vsce/releases)
- [Commits](microsoft/vscode-vsce@v2.22.0...v2.23.0)

Updates `chai` from 5.0.0 to 5.1.0
- [Release notes](https://github.com/chaijs/chai/releases)
- [Changelog](https://github.com/chaijs/chai/blob/main/History.md)
- [Commits](chaijs/chai@v5.0.0...v5.1.0)

Updates `esbuild` from 0.19.11 to 0.20.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.19.11...v0.20.0)

Updates `eslint-config-standard-with-typescript` from 43.0.0 to 43.0.1
- [Release notes](https://github.com/mightyiam/eslint-config-standard-with-typescript/releases)
- [Changelog](https://github.com/mightyiam/eslint-config-standard-with-typescript/blob/master/CHANGELOG.md)
- [Commits](mightyiam/eslint-config-love@v43.0.0...v43.0.1)

Updates `eslint-plugin-n` from 16.6.0 to 16.6.2
- [Release notes](https://github.com/eslint-community/eslint-plugin-n/releases)
- [Commits](eslint-community/eslint-plugin-n@16.6.0...16.6.2)

Updates `mocha` from 10.2.0 to 10.3.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v10.2.0...v10.3.0)

Updates `prettier` from 3.1.1 to 3.2.5
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.1.1...3.2.5)

Updates `prettier-eslint` from 16.2.0 to 16.3.0
- [Release notes](https://github.com/prettier/prettier-eslint/releases)
- [Changelog](https://github.com/prettier/prettier-eslint/blob/master/CHANGELOG.md)
- [Commits](prettier/prettier-eslint@v16.2.0...v16.3.0)

Updates `utility-types` from 3.10.0 to 3.11.0
- [Release notes](https://github.com/piotrwitek/utility-types/releases)
- [Commits](piotrwitek/utility-types@v3.10.0...v3.11.0)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@types/vscode"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@vscode/test-electron"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@vscode/vsce"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: chai
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-config-standard-with-typescript
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: eslint-plugin-n
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: mocha
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: prettier-eslint
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: utility-types
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

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 Feb 12, 2024
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 19, 2024

Superseded by #244.

@dependabot dependabot bot closed this Feb 19, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/dependencies-29842a6769 branch February 19, 2024 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants