Skip to content

chore: include src folder in package.json files #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 7, 2025
Merged

chore: include src folder in package.json files #24

merged 1 commit into from
Jul 7, 2025

Conversation

saseungmin
Copy link
Member

@saseungmin saseungmin commented Jul 7, 2025 •
edited by coderabbitai bot
Loading

  • Add src to files array for better debugging experience
  • Enables accurate source maps and stack traces for library users
  • Follows React Native library best practices

Summary by CodeRabbit

  • Chores
    • Improved package configuration to include the source directory, enhancing debugging support and aligning with best practices.

@saseungmin
chore: include src folder in package.json files
e141d2b 
- Add src to files array for better debugging experience
- Enables accurate source maps and stack traces for library users
- Follows React Native library best practices
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jul 7, 2025

🦋 Changeset detected

Latest commit: e141d2b

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

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 coderabbitai
Copy link

coderabbitai bot commented Jul 7, 2025 •
edited
Loading

Walkthrough

A changeset was added and the package.json file was updated to include the "src" directory in the "files" array for the "react-native-vimeo-bridge" package. No changes were made to exported or public entities, and no other package configuration was altered.

Changes

File(s) Change Summary
.changeset/solid-shoes-worry.md Added a changeset describing the inclusion of "src" in package files.
package.json Added "src" to the "files" array for package publishing.

Poem

A hop and a skip, a tweak to the pack,
Now "src" joins the files—no code does it lack!
Debugging is clearer, stack traces align,
The bridge to the vimeo world works just fine.
With a whisk of my paw and a satisfied cheer,
This rabbit says, "Ship it! The changes are here!" 🐇✨

📜 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 5cc11e6 and e141d2b.

📒 Files selected for processing (2)
  • .changeset/solid-shoes-worry.md (1 hunks)
  • package.json (1 hunks)
🔇 Additional comments (2)
package.json (1)

15-18: ‘src’ entry is a necessary addition — looks good

Adding "src" to the files array aligns what you publish with the exports.source field and avoids “module not found” problems for consumers using Metro to compile the TS sources. No issues spotted.

.changeset/solid-shoes-worry.md (1)

1-9: Changeset metadata and summary LGTM

Front-matter syntax is valid for Changesets, and the summary is clear and follows conventional-commit style. ✅

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@cloudflare-workers-and-pages Cloudflare Workers and Pages
Copy link

Deploying react-native-vimeo-bridge-example with  Cloudflare Pages  Cloudflare Pages

Latest commit: e141d2b
Status: ✅  Deploy successful!
Preview URL: https://bbe3505e.react-native-vimeo-bridge-example.pages.dev
Branch Preview URL: https://chore-add-src-to-package-fil.react-native-vimeo-bridge-example.pages.dev

View logs

@saseungmin saseungmin merged commit 5303b55 into main Jul 7, 2025
6 checks passed
@saseungmin saseungmin deleted the chore/add-src-to-package-files branch July 7, 2025 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@saseungmin