Version Packages (beta)

[Sec-ant]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

[email protected]

Patch Changes

• f8c33b2: Fix the zxing_writer.wasm size issue. See #190.

Summary by CodeRabbit

• New Version

  • Released version 2.0.0-beta.4
  • Updated package version to match changelog
  • Added new changeset configuration entry

• Bug Fixes

  • Addressed size issue with zxing_writer.wasm file

[coderabbitai]

Walkthrough

This pull request involves version updates for the zxing-wasm package from version 2.0.0-beta.3 to 2.0.0-beta.4. The changes include adding a new changeset entry in .changeset/pre.json, updating the version in package.json, and documenting the changes in CHANGELOG.md. The update appears to be a minor beta release addressing a size issue with the zxing_writer.wasm file.

Changes

File	Change Summary
.changeset/pre.json	Added new changeset entry "plenty-files-thank"
CHANGELOG.md	Updated to version 2.0.0-beta.4, documented size issue with zxing_writer.wasm
package.json	Updated version from 2.0.0-beta.3 to 2.0.0-beta.4

Possibly related PRs

• Version Packages #105: Updates to CHANGELOG.md and package.json for zxing-wasm, involving similar versioning changes

Poem

🐰 A beta hop, version four's delight,
Changesets dancing in the JSON light,
Wasm size trimmed with rabbit's care,
Package version leaps without a scare,
Coding magic, small and bright! 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f8c33b2 and 0a38a2c.

📒 Files selected for processing (3)

• .changeset/pre.json (1 hunks)
• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• package.json
• .changeset/pre.json

🔇 Additional comments (1)

CHANGELOG.md (1)

3-7: LGTM! Clear and well-documented changelog entry.

The changelog entry properly documents the patch change addressing the zxing_writer.wasm size issue, with a clear reference to the relevant discussion.

Let's verify the referenced discussion:

✅ Verification successful

Changelog entry correctly references the size issue discussion

The changelog entry accurately references discussion #190, which directly addresses the zxing_writer.wasm size issue. The discussion titled "Why is the v2 writer wasm binary so much larger?" confirms that this was a known issue where the writer binary size increased from ~366 KB to ~1.17 MB in v2 beta. The patch change documented in the changelog appears to be the fix for this size regression.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the referenced discussion exists and contains relevant context about the size issue
gh api graphql -f query='
{
  repository(owner: "Sec-ant", name: "zxing-wasm") {
    discussion(number: 190) {
      title
      body
      category {
        name
      }
    }
  }
}'

Length of output: 704

---

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.

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/zxing-wasm@192

commit: 0a38a2c