chore: bump deps

[Sec-ant]

Bump pnpm and deps, regenerate pnpm-lock file

Summary by CodeRabbit

• Chores
  • Upgraded internal development dependencies to maintain compatibility and stability.
  • Updated the package manager configuration to the latest version for enhanced performance.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 477d90c

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]

Walkthrough

This pull request updates the package.json file for the barcode-detector project. It upgrades several devDependencies—including various @commitlint, @vitest packages, playwright, vite, and @types/node—to their latest versions. Additionally, the packageManager field is updated to the new pnpm version. These changes ensure that the project stays compatible with the most recent releases of its dependencies.

Changes

File	Change Summary
package.json	Updated devDependencies versions for @commitlint/cli, @commitlint/config-conventional, @types/node, @vitest/browser, @vitest/coverage-istanbul, @vitest/ui, playwright, vite, and vitest; updated the packageManager to [email protected].

Possibly related PRs

• chore(deps-dev): bump the major-updates group across 1 directory with 6 updates #92: Involved similar updates to the @vitest packages in the package.json file, aligning dependency versions with recent releases.

Suggested labels

dependencies

Poem

(_/) Hi, I'm a coding bunny on a joyous spree,
Hopping through updates with glee and esprit.
Dependencies leap to newer heights in a graceful bound,
pnpm's fresh version makes our path sound.
I celebrate this change with a joyful hop—
Forward we code, never willing to stop!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 53c0002 and 477d90c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (4)

package.json (4)

120-125: Dependency Version Updates for Commitlint and Vitest Tools
The updated versions for @commitlint/cli, @commitlint/config-conventional, @types/node, @vitest/browser, @vitest/coverage-istanbul, and @vitest/ui look consistent with the latest releases. Please verify that these bumps do not introduce incompatibilities with your existing configurations or custom rules.

---

129-129: Playwright Update Review
The Playwright dependency has been bumped to ^1.50.1. Confirm that all browser automation and testing workflows are fully compatible with this version, as even minor updates can sometimes include breaking changes in tooling.

---

136-137: Vite and Vitest Upgrade Validation
Vite is updated to ^6.1.0 and Vitest to ^3.0.5. These upgrades should provide bug fixes and performance improvements. It is advisable to run a full build and test cycle to ensure that the build process and test suites operate seamlessly with these newer versions.

---

142-142: Package Manager Revision Notice
The packageManager field is now set to [email protected] and reflects a regenerated lockfile. Please ensure that local development, CI/CD processes, and deployment pipelines are compatible with this updated pnpm version to avoid any unforeseen issues.

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/barcode-detector@151

commit: 477d90c