chore: dependencies updated

[maehr]

Pull request

Proposed changes

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Summary by CodeRabbit

• Chores
  • Updated author and contributor information in project metadata for better clarity.
  • Upgraded multiple dependencies to their latest versions for improved performance and compatibility.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 75f7bec

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.

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]

Walkthrough

The pull request includes updates to the package.json file, focusing on the author and contributor information and upgrading multiple dependencies to their latest versions. The author details have been reformatted into a structured object, and two new contributors have been added. Additionally, various development dependencies have been updated, ensuring the project remains compatible with the latest library versions.

Changes

File	Change Summary
package.json	- Author information restructured to include name, email, and URL. - Two contributors added with names, emails, and URLs. - Multiple devDependencies updated to newer versions.

Poem

In the garden where code does bloom,
Dependencies dance, dispelling gloom.
With authors and friends, we gather near,
Upgrading our tools brings us cheer!
Hops of joy in every line,
A project refreshed, oh how divine! 🐇✨

---

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>, please review it.
  -- 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[coderabbitai]

Actionable comments posted: 1

Outside diff range and nitpick comments (1)

package.json (1)

9-20: LGTM: Contributors added

The addition of contributors is a positive change that properly acknowledges team members. The format is consistent with the author information, which is good for maintainability.

Consider adding a "contributors" field to your package.json schema if you haven't already. This can be done by adding the following to your package.json:

"$schema": "https://json.schemastore.org/package.json"

This will provide better IDE support and validation for the contributors field.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3a8c798 and 75f7bec.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (2 hunks)

Additional comments not posted (2)

package.json (2)

4-8: LGTM: Author information update

The author information has been updated to a more structured format, which is a good practice. This change improves the metadata quality of the package.json file.

---

Line range hint 1-87: Summary: Package.json updates look good overall

The changes to package.json are positive improvements:

1. Author information is now more structured.
2. Contributors have been properly acknowledged.
3. Dependencies have been updated to newer versions.

These changes enhance the project's metadata and keep the development environment up-to-date. Please ensure to run the verification script and address any potential issues that may arise from the dependency updates.