chore(deps): bump the minor-and-patch-updates group with 8 updates

[dependabot]

Bumps the minor-and-patch-updates group with 8 updates:

Package	From	To
type-fest	4.20.1	4.21.0
@changesets/cli	2.27.6	2.27.7
@types/node	20.14.9	20.14.10
esbuild	0.22.0	0.23.0
prettier-plugin-sql	0.18.0	0.18.1
tsx	4.16.0	4.16.2
typescript	5.5.2	5.5.3
vite	5.3.2	5.3.3

Updates type-fest from 4.20.1 to 4.21.0

Release notes

Sourced from type-fest's releases.

v4.21.0

New types

• StructuredCloneable (#897) 737550b

Fixes

• Jsonify: Convert undefined to null in union element of array (#901) 60c1024
• Exact: Fix support for Date in union (#902) d89a709
• CamelCasedPropertiesDeep: Fix handling of non-recursive types inside target type (#890) 476024d

sindresorhus/type-fest@v4.20.1...v4.21.0

Commits

• 60712f1 4.21.0
• d89a709 Exact: Fix support for Date in union (#902)
• 60c1024 Jsonify: Convert undefined to null in union element of array (#901)
• bdfc391 Bump typescript from 5.4.5 to 5.5.3 in the development-dependencies group (#903)
• 476024d CamelCasedPropertiesDeep: Fix handling of non-recursive types inside target...
• 737550b Add StructuredCloneable type (#897)
• dc35412 Remove DOM lib dependence in tsconfig (#898)
• 0e46755 IterableElement: Improve docs and add tests for using it with Set (#894)
• e75dbe1 IntRange: Document lack of support for negative numbers
• See full diff in compare view

Updates @changesets/cli from 2.27.6 to 2.27.7

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.27.7

Patch Changes

• #1047 d108fa6 Thanks @​patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package.

• #1400 dd6e5bb Thanks @​Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspace

• Updated dependencies [d108fa6, dd6e5bb, dd6e5bb]:

  • @​changesets/apply-release-plan@​7.0.4
  • @​changesets/config@​3.0.2
  • @​changesets/get-dependents-graph@​2.1.1
  • @​changesets/assemble-release-plan@​6.0.3
  • @​changesets/get-release-plan@​4.0.3

Commits

• b593756 Version Packages (#1398)
• d83e458 Update changelog for privatePackage fix (#1402)
• dd6e5bb Fixed a crash when root workspace has dependents (#1400)
• d108fa6 Fixed a crash when using tag versions of workspace packages (#1047)
• a832b64 fix typo in automating-changesets.md (#1155)
• See full diff in compare view

Updates @types/node from 20.14.9 to 20.14.10

Commits

• See full diff in compare view

Updates esbuild from 0.22.0 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>;

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>;

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
• See full diff in compare view

Updates prettier-plugin-sql from 0.18.0 to 0.18.1

Release notes

Sourced from prettier-plugin-sql's releases.

[email protected]

Patch Changes

• #374 6754c3d Thanks @​JounQin! - fix(sql): printer to handle eol correctly

Commits

• a818d8f chore: release package(s) (#375)
• 1670d7e Update README.md to match package.json (#363)
• 3b084b6 docs: update prettier-plugin-embed usage (#364)
• 6754c3d fix(sql): printer to handle eol correctly (#374)
• 947b0af ci: upgrade to pnpm/action-setup@v4
• b86d38e chore(deps): update dependency @​types/web to ^0.0.150
• 2cec244 chore(deps): update dependency @​changesets/cli to ^2.27.6
• 089f487 fix(deps): update dependency sh-syntax to ^0.4.2
• 99f769d chore(deps): update dependency unplugin-auto-import to ^0.17.6
• 3d277f1 chore(deps): update dependency @​types/web to ^0.0.147
• Additional commits viewable in compare view

Updates tsx from 4.16.0 to 4.16.2

Release notes

Sourced from tsx's releases.

v4.16.2

4.16.2 (2024-07-03)

Bug Fixes

• isolated cts import in Node v18 (#61) (042be03)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.16.1

4.16.1 (2024-07-03)

Bug Fixes

• cjs: isolate implicit resolver enhancement (#59) (143a5bd)
• cjs: namespace filter to preserve file path (6ef949c)
• esm: implicit resolution with tsconfig paths (a74aa58), closes #607

---

This release is also available on:

• npm package (@​latest dist-tag)

Commits

• 042be03 fix: isolated cts import in Node v18 (#61)
• a74aa58 fix(esm): implicit resolution with tsconfig paths
• 1603c66 refactor(cjs): cjs lexer detection
• c6d5203 refactor(cjs): always inherit query from parent (#60)
• aa3f2a1 test: scoped cts loading in Node v18
• 8c61236 refactor(types): improve CJS module types
• 23ebe7e refactor: preserve resolveFilename args accurately
• e0b581c test: assert package can be loaded relative to data url
• 143a5bd fix(cjs): isolate implicit resolver enhancement (#59)
• 6ef949c fix(cjs): namespace filter to preserve file path
• See full diff in compare view

Updates typescript from 5.5.2 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

Commits

• f0e9921 Bump version to 5.5.3 and LKG
• 738bd60 Cherry-pick #58966 to release-5.5 (#59002)
• See full diff in compare view

Updates vite from 5.3.2 to 5.3.3

Changelog

Sourced from vite's changelog.

5.3.3 (2024-07-03)

• fix: lazily evaluate __vite__mapDeps files (#17602) (dafff4a), closes #17602
• fix(deps): update all non-major dependencies (#17590) (012490c), closes #17590
• fix(lib): remove pure CSS dynamic import (#17601) (055f1c1), closes #17601
• fix(proxy): replace changeOrigin changes in 5.3.0 with new rewriteWsOrigin option (#17563) (14c3d49), closes #17563

Commits

• 22b2994 release: v5.3.3
• 012490c fix(deps): update all non-major dependencies (#17590)
• 14c3d49 fix(proxy): replace changeOrigin changes in 5.3.0 with new rewriteWsOrigin op...
• 055f1c1 fix(lib): remove pure CSS dynamic import (#17601)
• dafff4a fix: lazily evaluate __vite__mapDeps files (#17602)
• See full diff 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5ec9573

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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