search

pester / vscode-adapter

Run PowerShell Pester Tests with Visual Studio Code
MIT License
58 stars 13 forks source link

Bump the dependencies group with 12 updates #239

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 7 months ago

Bumps the dependencies group with 12 updates:

Package From To
@types/node 20.10.6 20.11.10
@typescript-eslint/eslint-plugin 6.16.0 6.19.1
@typescript-eslint/parser 6.16.0 6.19.1
@vscode/test-electron 2.3.8 2.3.9
@vscode/vsce 2.22.0 2.23.0
chai 5.0.0 5.0.3
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
prettier 3.1.1 3.2.4
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.10

Commits


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

Release notes

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

v6.19.1

6.19.1 (2024-01-22)

🩹 Fixes

  • eslint-plugin: [no-unnecessary-condition] fix false positive for type variable (#8235)
  • type-utils: preventing isUnsafeAssignment infinite recursive calls (#8237)

❤️ Thank You

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

v6.19.0

6.19.0 (2024-01-15)

🚀 Features

  • eslint-plugin: [prefer-promise-reject-errors] add rule (#8011)
  • eslint-plugin: [no-array-delete] add new rule (#8067)
  • eslint-plugin: [no-useless-template-literals] add fix suggestions (#8065)

🩹 Fixes

  • eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression (#8143)
  • eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable (#8089)
  • typescript-estree: add JSDocParsingMode enum merge for typescript/lib/tsserverlibrary (#8193)
  • typescript-estree: disallow using as the variable keyword for for..in loops (#7649)
  • typescript-estree: fix incorrect backwards-compat augmentation in TS 5.3 (#8181)

❤️ Thank You

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

v6.18.1

6.18.1 (2024-01-08)

🩹 Fixes

... (truncated)

Changelog

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

6.19.1 (2024-01-22)

🩹 Fixes

  • type-utils: preventing isUnsafeAssignment infinite recursive calls

  • eslint-plugin: [no-unnecessary-condition] fix false positive for type variable

❤️ Thank You

  • YeonJuan

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

6.19.0 (2024-01-15)

🚀 Features

  • eslint-plugin: [prefer-promise-reject-errors] add rule

  • eslint-plugin: [no-array-delete] add new rule

  • eslint-plugin: [no-useless-template-literals] add fix suggestions

🩹 Fixes

  • eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression

  • eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable

❤️ Thank You

  • auvred
  • Brad Zacher
  • Josh Goldberg ✨
  • Joshua Chen
  • LJX
  • Steven
  • StyleShit

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

6.18.1 (2024-01-08)

... (truncated)

Commits
  • a911214 chore(release): publish 6.19.1
  • 920f909 fix(eslint-plugin): [no-unnecessary-condition] fix false positive for type va...
  • 01556f5 fix(type-utils): preventing isUnsafeAssignment infinite recursive calls (#8237)
  • 7c673a1 chore(release): publish 6.19.0
  • 85ae4a8 fix(eslint-plugin): [no-unnecesary-type-assertion] treat unknown/any as nulla...
  • 5a56708 fix(eslint-plugin): [no-unnecessary-type-assertion] detect unnecessary non-nu...
  • c3767ed feat(eslint-plugin): [no-useless-template-literals] add fix suggestions (#8065)
  • 8ca5e5e docs: force space after await in no-floating-promises snippet (#8228)
  • e0f591e feat(eslint-plugin): [no-array-delete] add new rule (#8067)
  • 1aa8664 feat(eslint-plugin): [prefer-promise-reject-errors] add rule (#8011)
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 6.16.0 to 6.19.1

Release notes

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

v6.19.1

6.19.1 (2024-01-22)

🩹 Fixes

  • eslint-plugin: [no-unnecessary-condition] fix false positive for type variable (#8235)
  • type-utils: preventing isUnsafeAssignment infinite recursive calls (#8237)

❤️ Thank You

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

v6.19.0

6.19.0 (2024-01-15)

🚀 Features

  • eslint-plugin: [prefer-promise-reject-errors] add rule (#8011)
  • eslint-plugin: [no-array-delete] add new rule (#8067)
  • eslint-plugin: [no-useless-template-literals] add fix suggestions (#8065)

🩹 Fixes

  • eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression (#8143)
  • eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable (#8089)
  • typescript-estree: add JSDocParsingMode enum merge for typescript/lib/tsserverlibrary (#8193)
  • typescript-estree: disallow using as the variable keyword for for..in loops (#7649)
  • typescript-estree: fix incorrect backwards-compat augmentation in TS 5.3 (#8181)

❤️ Thank You

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

v6.18.1

6.18.1 (2024-01-08)

🩹 Fixes

... (truncated)

Changelog

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

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)

Note: Version bump only for package @​typescript-eslint/parser

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

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

Release notes

Sourced from chai's releases.

v5.0.3

Fix bad v5.0.2 publish.

Full Changelog: https://github.com/chaijs/chai/compare/v5.0.2...v5.0.3

v5.0.2

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/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 prettier from 3.1.1 to 3.2.4

Release notes

Sourced from prettier's releases.

3.2.4

  • Fix .eslintrc.json format #15947

🔗 Changelog

3.2.3

  • Format tsconfig.json file with jsonc parser #15927

🔗 Changelog

3.2.2

🔗 Changelog

3.2.1

🔗 Changelog

3.2.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.2.4

diff

Fix incorrect parser inference (#15947 by @​fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }

3.2.3

diff

Throw errors for invalid code (#15881 by @​fisker, @​Josh-Cena, @​auvred)

// Input
1++;

// Prettier 3.2.2
1++;


// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
| ^


// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
</tr></table>

... (truncated)

Commits


Updates prettier-eslint from 16.2.0 to 16.3.0

Release notes

Sourced from prettier-eslint's releases.

v16.3.0

Minor Changes

New Contributors

Full Changelog: https://github.com/prettier/prettier-eslint/compare/v16.2.0...v16.3.0

Changelog

Sourced from prettier-eslint's changelog.

16.3.0

Minor Changes

Commits
Maintainer changes

This version was pushed to npm by jounqin, a new releaser for prettier-eslint since your current version.


Updates utility-types from 3.10.0 to 3.11.0

Release notes

Sourced from utility-types's releases.

v3.11.0

What's Changed

New Contributors

Full Changelog: https://github.com/piotrwitek/utility-types/compare/v3.10.0...v3.11.0

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 6 months ago

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