chore: bump zxing-cpp and other dependencies

[Sec-ant]

Summary by CodeRabbit

• Chores
  • Updated various dependencies to their latest versions for improved performance and security.
  • Ensured consistent use of .js as the chunk filename extension.
  • Updated zxing-cpp module to version 986f785.

[changeset-bot]

🦋 Changeset detected

Latest commit: 20d8e73

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
zxing-wasm	Patch

Not sure what this means? Click here to learn what changesets are.

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

[coderabbitai]

Walkthrough

The recent updates encompass dependency upgrades in package.json, including key libraries such as @babel/core, @babel/types, and prettier. Additionally, the zxing-cpp module has been updated to version 986f785. These changes aim to enhance performance, maintain compatibility, and ensure the latest features and security updates are incorporated.

Changes

File/Path	Change Summary
.changeset/yellow-keys-drive.md	Added a new changeset detailing updates to zxing-wasm and zxing-cpp, and dependency bumps.
package.json	Updated dependencies including @babel/core, @babel/types, @biomejs/biome, prettier, and more.
zxing-cpp	Updated subproject commit hash to version 986f785.

Poem

In code's vast garden, dependencies bloom,
With updates and bumps, they dispel the gloom.
zxing-cpp now shines anew,
As prettier and friends join the crew.
Together they dance, in harmony's tune,
Making our codebase a bright, sunny noon. 🌞

---

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.

[pkg-pr-new]

Run & review this pull request in StackBlitz Codeflow.

zxing-wasm (20d8e73)

npm i https://pkg.pr.new/zxing-wasm@110

null

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f11a05b and 20d8e73.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (3)

• .changeset/yellow-keys-drive.md (1 hunks)
• package.json (1 hunks)
• zxing-cpp (1 hunks)

Files skipped from review due to trivial changes (2)

• .changeset/yellow-keys-drive.md
• zxing-cpp

Additional comments not posted (10)

package.json (10)

98-98: Update to @babel/core looks good and follows semantic versioning.

---

99-99: Update to @babel/types is appropriate and minor, aligning with semantic versioning.

---

100-100: Update to @biomejs/biome correctly increments the minor version, suggesting non-breaking changes.

---

101-101: Minor version update for @changesets/cli is correctly applied.

---

103-103: Update to @types/node follows proper versioning practices.

---

106-106: Update to lint-staged is minor and follows semantic versioning.

---

108-108: Update to prettier is minor and correctly follows semantic versioning.

---

112-112: Update to tsx is minor and correctly follows semantic versioning.

---

115-115: Update to vite is minor and correctly follows semantic versioning.

---

119-119: Update to @types/emscripten is minor and correctly follows semantic versioning.