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

[dependabot]

Bumps the minor-and-patch-updates group with 4 updates: @changesets/cli, @types/node, esbuild and tsx.

Updates @changesets/cli from 2.27.1 to 2.27.2

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.27.2

Patch Changes

• #1354 69be7dc Thanks @​Andarist! - Fixed an issue with changeset status incorrectly returning an error status in two cases:

  • for changed ignored packages
  • for changed private packages when privatePackage.version was set to false

• #1351 c6da182 Thanks @​TheHolyWaffle! - Fix an issue with not applying a custom .prettierrc configuration with prettier@>= 3.1.1

• Updated dependencies [c6da182]:

  • @​changesets/apply-release-plan@​7.0.1
  • @​changesets/write@​0.3.1

Commits

• 4b60580 Version Packages (#1355)
• 69be7dc Fixed changeset status combined with ignored and non-versionable private pa...
• c6da182 Fix an issue with not applying a custom .prettierrc configuration with `pre...
• 0bf89b3 Use node 20.x in release flow (#1333)
• 4185510 Fix incorrect plural (#1310)
• 93ee679 Add SECURITY.md
• See full diff in compare view

Updates @types/node from 20.12.11 to 20.12.12

Commits

• See full diff in compare view

Updates esbuild from 0.21.2 to 0.21.3

Release notes

Sourced from esbuild's releases.

v0.21.3

• Implement the decorator metadata proposal (#3760)

  This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
  }
  class Foo {
  @​track foo = 1
  @​track bar = 2
  }
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes (#3768)

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories (#3767)

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

Changelog

Sourced from esbuild's changelog.

0.21.3

• Implement the decorator metadata proposal (#3760)

  This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
  }
  class Foo {
  @​track foo = 1
  @​track bar = 2
  }
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes (#3768)

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories (#3767)

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

Commits

• efa3dd2 publish 0.21.3 to npm
• 5e7cf25 fix #3760: implement decorator metadata proposal
• bd0b13b lowering: always propagate class expression names
• 90acd14 explicit bitwise operators for initializer flags
• ba548df move decorator initializer list to after the class
• 66b7c6d fix #3768: bundled decorators in derived classes
• 6e6f15f fix #3767: tsconfig.json files inside symlinks
• b7dcb95 transform: reuse lowerField for auto-accessors
• See full diff in compare view

Updates tsx from 4.10.1 to 4.10.5

Release notes

Sourced from tsx's releases.

v4.10.5

4.10.5 (2024-05-18)

Bug Fixes

• handle parsing variable of (86cf87c), closes #556

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.10.4

4.10.4 (2024-05-17)

Bug Fixes

• cjs: support file url (#18) (4a8a2dc)
• V8 coverage support (942e9bc), closes privatenumber/tsx#433

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.10.3

4.10.3 (2024-05-16)

Performance Improvements

• skip parsing if import( is not found in minified code (5cdd50b)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.10.2

4.10.2 (2024-05-13)

... (truncated)

Commits

• 86cf87c fix: handle parsing variable of
• 4a8a2dc fix(cjs): support file url (#18)
• 942e9bc fix: V8 coverage support
• 05c382f style(parseEsm): make filename optional
• 5cdd50b perf: skip parsing if import( is not found in minified code
• ad970ac chore: improve issue template
• 0a989d9 docs: fix broken links (#555)
• e2afc60 chore: improve issue templates
• 0e66aed chore: upgrade deps
• 2c87fc1 fix: expose types for esm/api (#551)
• 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0aa91c

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

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

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.