chore: increase payment-widget version

[aimensahnoun]

Resolves #144

Update the payment widget version to make a release with the latest added features:

• Exposing fee address and fee amount
• Ability to download receipts and redirect to request scan

Summary by CodeRabbit

• New Features

  • Updated the version of the payment widget to 0.2.0, enhancing compatibility and functionality.

• Chores

  • Maintained and organized dependencies for improved performance and stability.

[coderabbitai]

Walkthrough

The pull request updates the package.json file for the @requestnetwork/payment-widget package. Key changes include a version increment from 0.1.4 to 0.2.0, and adjustments to the exports, peerDependencies, and devDependencies sections. The files array specifies included files, while the type field is set to module, indicating ES module usage. The license remains MIT, and the publishConfig ensures public access upon publishing.

Changes

File Path	Change Summary
packages/payment-widget/package.json	- Version updated to 0.2.0 - Adjusted exports, peerDependencies, and devDependencies - Maintained files, type, and license fields

Assessment against linked issues

Objective	Addressed	Explanation
Release new Payment Widget version (#144)	❌	The PR does not implement the new features specified in the issue.

Possibly related PRs

• feat: improve responsiveness for payment widget #120: Improves the responsiveness of the payment widget, related to the @requestnetwork/payment-widget package.
• chore: increase package size for release #125: Updates the version number of the @requestnetwork/payment-widget package, aligning with the main PR.
• chore: add payment-widget to release process #132: Integrates the @requestnetwork/payment-widget into the release process, relevant to the changes in the main PR.
• feat: enable custom fee address and fee amount #140: Introduces new properties to the payment-widget.svelte component, enhancing its functionality related to the @requestnetwork/payment-widget package.
• feat: add receipt export and viewing on request scan #142: Enhances the payment widget's functionality by adding receipt export features, relevant to the overall improvements in the @requestnetwork/payment-widget package.

Suggested reviewers

• sstefdev
• rodrigopavezi

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 20e1554 and b34ac4d.

📒 Files selected for processing (1)

• packages/payment-widget/package.json (1 hunks)

🔇 Additional comments (2)

packages/payment-widget/package.json (2)

3-3: Version bump approved

The version update from 0.1.4 to 0.2.0 is appropriate for a minor release that includes new features. This aligns with the PR objectives of exposing fee address and fee amount, adding functionality for downloading receipts, and redirecting to a request scan after payment.

---

Line range hint 1-70: Verify dependency updates for new features

The PR objectives mention new features being added, but there are no visible changes to the dependencies. Please verify if any new dependencies are required or if existing dependencies need to be updated to support the new features (exposing fee address and fee amount, downloading receipts, and redirecting to request scan after payment).

✅ Verification successful

---

Dependency Updates Verified

No changes to dependencies are required for the new features. All necessary dependencies are already present and appropriately utilized.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any changes in dependencies related to the new features

# Test 1: Check if there are any changes in package.json related to dependencies
git diff origin/main -- packages/payment-widget/package.json | grep -E "dependencies|devDependencies"

# Test 2: Check if there are any new imports in the widget's source files that might indicate new dependencies
rg --type typescript -g '!*.test.ts' -g '!*.spec.ts' --no-heading --no-line-number 'import .* from' packages/payment-widget/src

# Test 3: Check for any TODO comments related to dependencies or the new features
rg --type typescript -g '!*.test.ts' -g '!*.spec.ts' --no-heading --no-line-number 'TODO' packages/payment-widget/src

Length of output: 421

---

Script:

#!/bin/bash
# Description: Corrected script to check for any changes in dependencies related to the new features

# Test 1: Check if there are any changes in package.json related to dependencies
git diff origin/main -- packages/payment-widget/package.json | grep -E "dependencies|devDependencies"

# Test 2: Check if there are any new imports in the widget's source files that might indicate new dependencies
rg --glob '*.ts' --glob '*.tsx' --type-add 'typescript:*.ts,*.tsx' --no-heading --no-line-number 'import .* from' packages/payment-widget/src

# Test 3: Check for any TODO comments related to dependencies or the new features
rg --glob '*.ts' --glob '*.tsx' --no-heading --no-line-number 'TODO' packages/payment-widget/src

Length of output: 1592

---

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.

[MantisClone]

@aimensahnoun
For future reference, I think it'd be useful to include in the PR description links to the PRs being released as part of this version number bump.