deps(deps-dev): bump the development-dependencies group with 7 updates

[dependabot]

Bumps the development-dependencies group with 7 updates:

Package	From	To
@typescript-eslint/eslint-plugin	6.19.0	6.20.0
@typescript-eslint/parser	6.19.0	6.20.0
prettier	3.2.2	3.2.4
@types/node	20.11.4	20.11.15
esbuild	0.19.11	0.20.0
@web/dev-server	0.4.1	0.4.2
alpinejs	3.13.3	3.13.5

Updates @typescript-eslint/eslint-plugin from 6.19.0 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.

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.

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

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.

Commits

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

Updates prettier from 3.2.2 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

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

• 03822f5 Release 3.2.4
• 1cd4d9c Fix JSONC filenames list (#15947)
• 6c6a332 Spellcheck
• 75ec1f7 Fix lock file
• dda00cd Clean changelog_unreleased
• c12e3c6 Git blame ignore 3.2.3
• 4985be5 Bump Prettier dependency to 3.2.3
• 38c0d21 Update dependents count
• 42ba437 Release 3.2.3
• 99c873d chore(deps): update typescript-eslint to v6.19.0 (#15939)
• Additional commits viewable in compare view

Updates @types/node from 20.11.4 to 20.11.15

Commits

• See full diff 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 @web/dev-server from 0.4.1 to 0.4.2

Release notes

Sourced from @​web/dev-server's releases.

@​web/dev-server@​0.4.2

Patch Changes

• 649edc2b: Add option to modify chokidar watchOptions with @​web/dev-server
• Updated dependencies [649edc2b]
  • @​web/dev-server-core@​0.7.1

Changelog

Sourced from @​web/dev-server's changelog.

0.4.2

Patch Changes

• 649edc2b: Add option to modify chokidar watchOptions with @​web/dev-server
• Updated dependencies [649edc2b]
  • @​web/dev-server-core@​0.7.1

Commits

• 6a1ed05 Version Packages
• fa46b6c feat: Add option to modify chokidar watchOptions with @​web/dev-server
• 90e4472 ci: use workspaces to run node tests
• See full diff in compare view

Updates alpinejs from 3.13.3 to 3.13.5

Release notes

Sourced from alpinejs's releases.

v3.13.5

Fixed

• 🐛 Fixes reinitializing moved elements #3995
• Add better entangle infinite-loop protection alpinejs/alpine@8001383

v3.13.4

What's Changed

• Improve combobox performance by @​calebporzio in alpinejs/alpine#3898
• [Docs] Add range type to x-model inputs by @​peterfox in alpinejs/alpine#3911
• Fix x-id when used with morph by @​calebporzio in alpinejs/alpine#3919
• Rework mutation observer by @​calebporzio in alpinejs/alpine#3929
• add explanation of passing an object to x-for by @​browner12 in alpinejs/alpine#3928
• x-mask: Cleanup of event listeners by @​beholdr in alpinejs/alpine#3908
• Update refs.md by @​Simsz in alpinejs/alpine#3851
• Add CSP-friendly Alpine build by @​calebporzio in alpinejs/alpine#3959
• docs: typo by @​mhanberg in alpinejs/alpine#3960
• Bug in code example of documentation for x-anchor to an ID by @​MaximVanhove in alpinejs/alpine#3942
• Fix typo by @​aerni in alpinejs/alpine#3932
• 🐛 Gracefully handles bad throws by @​ekwoka in alpinejs/alpine#3570
• Fix x-mask when used with wire:model by @​calebporzio in alpinejs/alpine#3988
• Fix issue where error message would not print directive name properly by @​mattvague in alpinejs/alpine#3572
• Add named exports to build files by @​ypconstante in alpinejs/alpine#3644
• fix: reset input on init so default value is displayed by @​coder2000 in alpinejs/alpine#3881
• Clear combobox bugfix by @​gdebrauwer in alpinejs/alpine#3934
• fix/x-model with fill modifier takes input value on undefined by @​rgbc-alex in alpinejs/alpine#3941
• fix: already init component by @​Matsa59 in alpinejs/alpine#3951
• Listbox compare null value bugfix by @​gdebrauwer in alpinejs/alpine#3962
• Fix error message in listbox.js by @​gdebrauwer in alpinejs/alpine#3965
• Add x-trap noinitialfocus modifier by @​richcarni in alpinejs/alpine#3977
• Combobox and listbox: Save optionKey in x-data to fix usage in Livewire by @​gdebrauwer in alpinejs/alpine#3990

New Contributors

• @​peterfox made their first contribution in alpinejs/alpine#3911
• @​beholdr made their first contribution in alpinejs/alpine#3908
• @​Simsz made their first contribution in alpinejs/alpine#3851
• @​MaximVanhove made their first contribution in alpinejs/alpine#3942
• @​aerni made their first contribution in alpinejs/alpine#3932
• @​mattvague made their first contribution in alpinejs/alpine#3572
• @​ypconstante made their first contribution in alpinejs/alpine#3644
• @​coder2000 made their first contribution in alpinejs/alpine#3881
• @​rgbc-alex made their first contribution in alpinejs/alpine#3941
• @​Matsa59 made their first contribution in alpinejs/alpine#3951
• @​richcarni made their first contribution in alpinejs/alpine#3977

Full Changelog: alpinejs/alpine@v3.13.3...v3.13.4

Commits

• 973cfe9 bump to 3.13.5
• e394287 🐛 Fixes reinitializing moved elements (#3995)
• 0bf054e wip
• 8001383 Add better entanglement infinite-loop protection
• 6918d96 bump to 3.13.4
• aa3375a remove console.log
• cb1e3ac Merge branch 'Omerlo-Technologies/main'
• 3196c6a tweak implementation
• 35f9ac1 x-model with fill modifier takes input value on null, empty string or undefin...
• aed412b Add named exports to build files (#3644)
• 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

[dependabot]

The following labels could not be found: dependencies, ci, priority-low, maintenance.

[dependabot]

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