chore(deps-dev): bump the dev-dependencies group with 10 updates

[dependabot]

Bumps the dev-dependencies group with 10 updates:

Package	From	To
@typescript-eslint/eslint-plugin	6.18.1	6.20.0
@typescript-eslint/parser	6.18.1	6.20.0
cypress	13.6.2	13.6.4
esbuild	0.19.11	0.20.0
npm-check-updates	16.14.12	16.14.14
stylelint	16.1.0	16.2.0
@types/react	18.2.47	18.2.48
vite	5.0.11	5.0.12
@types/luxon	3.4.0	3.4.2
@types/node	18.19.6	18.19.11

Updates @typescript-eslint/eslint-plugin from 6.18.1 to 6.20.0

Release notes

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

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

• Alex Parloti @​parloti
• auvred @​auvred
• James Browning
• StyleShit @​StyleShit
• YeonJuan @​yeonjuan

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

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

• YeonJuan @​yeonjuan

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)

... (truncated)

Changelog

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

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

• eslint-plugin: [no-useless-template-literals] report Infinity & NaN

• eslint-plugin: [prefer-readonly] disable checking accessors

❤️ Thank You

• Alex Parloti
• auvred
• James Browning
• StyleShit
• YeonJuan

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

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

... (truncated)

Commits

• a01a6e6 chore(release): publish 6.20.0
• 4d2ce3b fix(eslint-plugin): [prefer-readonly] disable checking accessors (#8300)
• 9dca40e chore(eslint-plugin): fix typos in schema definitions (#8311)
• d02d086 fix(eslint-plugin): [no-useless-template-literals] report Infinity & NaN (#8295)
• 70505e4 fix(eslint-plugin): [prefer-nullish-coalescing] treat any/unknown as non-null...
• d0137c8 chore: enable prefer-nullish-coalescing internally (#7955)
• bbc6770 feat(eslint-plugin): [member-ordering] allow easy reuse of the default orderi...
• 8622286 fix(eslint-plugin): [no-useless-template-literals] incorrect bigint autofix r...
• a911214 chore(release): publish 6.19.1
• 920f909 fix(eslint-plugin): [no-unnecessary-condition] fix false positive for type va...
• Additional commits viewable in compare view

Updates @typescript-eslint/parser from 6.18.1 to 6.20.0

Release notes

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

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

• Alex Parloti @​parloti
• auvred @​auvred
• James Browning
• StyleShit @​StyleShit
• YeonJuan @​yeonjuan

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

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

• YeonJuan @​yeonjuan

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)

... (truncated)

Changelog

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

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.

Commits

• a01a6e6 chore(release): publish 6.20.0
• a911214 chore(release): publish 6.19.1
• 7c673a1 chore(release): publish 6.19.0
• See full diff in compare view

Updates cypress from 13.6.2 to 13.6.4

Release notes

Sourced from cypress's releases.

v13.6.4

Changelog: https://docs.cypress.io/guides/references/changelog#13-6-4

v13.6.3

Changelog: https://docs.cypress.io/guides/references/changelog#13-6-3

Commits

• f705980 chore: bump package.json and format changelog for release 13.6.4 (#28825)
• f21b4a1 chore: release @​cypress/webpack-dev-server-v3.7.4
• 43792e7 fix: optimize reduce addCypressToWebpackEslintRulesInPlace (#27819)
• 6842d1e chore: Update Chrome (beta) to 122.0.6261.6 (#28797)
• f741635 chore: Update Chrome (stable) to 121.0.6167.85 (#28786)
• 1b5eac9 chore: fix release readiness job [run ci] (#28790)
• c415c81 chore: update octokit and arm64 image to newest focal (#28754)
• 9088dc2 fix: issue with service workers in test replay when they're initiated from a ...
• b17409a chore(deps): update dependency vite [security] (#28773)
• bf923fb chore: Update Chrome (beta) to 121.0.6167.85 (#28778)
• Additional commits viewable in compare view

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

• 2af5ccf publish 0.20.0 to npm
• 0bccf08 fix esbuild/deno-esbuild#5
• 931f87d work around api deprecations in deno 1.40.x (#3609) (#3611)
• 22a9cf5 fix #3341, fix #3608: sort .ts right after .js
• f8ec300 run npm pkg fix as suggested by the npm cli
• d7fd1ad publish 0.19.12 to npm
• e04a690 fix #3605: print the original JSX AST unmodified
• f571399 allow jsx elements as jsx attribute values
• a652e73 run make update-compat-table
• 35c0d65 fix #3574: ts type parser bug with infer + extends
• Additional commits viewable in compare view

Updates npm-check-updates from 16.14.12 to 16.14.14

Commits

• 9803875 16.14.14
• cd705ec global: Fix package manager args destructuring (#1365).
• a86905b global: Program error on getInstalledPackages error.
• 7c88f2d 16.14.13
• bde6878 spawnYarn: args must go after yarn options (#1362).
• 94a9128 refactor: pnpm and yarn
• 4ab2c9d post-commit: Remove git commit from notification title.
• 6bac31a Remove husky.
• See full diff in compare view

Updates stylelint from 16.1.0 to 16.2.0

Release notes

Sourced from stylelint's releases.

16.2.0

• Added: media-query-no-invalid specific problem messages (#7462) (@​romainmenke).
• Added: checkContextFunctionalPseudoClasses: [] to selector-max-id (#7380) (@​brigitamaria).
• Fixed: declaration-property-value-no-unknown false negatives for @starting-style (#7461) (@​fpetrakov).
• Fixed: function-no-unknown|value-keyword-case false positives for template literals with line breaks (#7443) (@​Sh031224).
• Fixed: allowEmptyInput option ignored in configuration object regression (#7446) (@​ybiquitous).
• Fixed: at-rule-no-unknown false positives for @starting-style (#7438) (@​fpetrakov).
• Fixed: ERR_UNSUPPORTED_ESM_URL_SCHEME for --custom-formatter on Windows (#7432) (@​JounQin).
• Fixed: Error: Could not find <package> message clarity (#7456) (@​jeddy3).
• Fixed: overrides.files negated pattern regression introduced in 15.0.0 (#7468) (@​ybiquitous).

Changelog

Sourced from stylelint's changelog.

16.2.0

• Added: media-query-no-invalid specific problem messages (#7462) (@​romainmenke).
• Added: checkContextFunctionalPseudoClasses: [] to selector-max-id (#7380) (@​brigitamaria).
• Fixed: declaration-property-value-no-unknown false negatives for @starting-style (#7461) (@​fpetrakov).
• Fixed: function-no-unknown|value-keyword-case false positives for template literals with line breaks (#7443) (@​Sh031224).
• Fixed: allowEmptyInput option ignored in configuration object regression (#7446) (@​ybiquitous).
• Fixed: at-rule-no-unknown false positives for @starting-style (#7438) (@​fpetrakov).
• Fixed: ERR_UNSUPPORTED_ESM_URL_SCHEME for --custom-formatter on Windows (#7432) (@​JounQin).
• Fixed: Error: Could not find <package> message clarity (#7456) (@​jeddy3).
• Fixed: overrides.files negated pattern regression introduced in 15.0.0 (#7468) (@​ybiquitous).

Commits

• f4c75c9 16.2.0
• 1b11ba3 Prepare 16.2.0 (#7439)
• 39ccfe9 Document CLI piping example (#7469)
• 38e0606 Fix overrides.files negated pattern regression (#7468)
• d881c9d Fix declaration-property-value-no-unknown false negatives for `@starting-st...
• e0754a9 Bump postcss-html from 1.5.0 to 1.6.0 (#7466)
• 77e005b Bump rollup from 4.9.4 to 4.9.5 (#7465)
• 29a57e1 Bump the typescript group with 1 update (#7464)
• c89a5a2 Bump the eslint group with 1 update (#7463)
• 5bb517b Add media-query-no-invalid specific problem messages (#7462)
• Additional commits viewable in compare view

Updates @types/react from 18.2.47 to 18.2.48

Commits

• See full diff in compare view

Updates vite from 5.0.11 to 5.0.12

Changelog

Sourced from vite's changelog.

5.0.12 (2024-01-19)

• fix: await configResolved hooks of worker plugins (#15597) (#15605) (ef89f80), closes #15597 #15605
• fix: fs deny for case insensitive systems (#15653) (91641c4), closes #15653

Commits

• ee81e19 release: v5.0.12
• 91641c4 fix: fs deny for case insensitive systems (#15653)
• ef89f80 fix: await configResolved hooks of worker plugins (#15597) (#15605)
• See full diff in compare view

Updates @types/luxon from 3.4.0 to 3.4.2

Commits

• See full diff in compare view

Updates @types/node from 18.19.6 to 18.19.11

Commits

• See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
@types/node	[>= 20.a, < 21]

You can trigger a rebase of this PR 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

[dependabot]

Superseded by #907.