chore(npm): Add website, .devcontainer to npmignore

[yamadashy]

• chore(npm): Add website, .devcontainer to npmignore
• fix(package): Fix package.json exports section

Checklist

• Run npm run test
• Run npm run lint

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[cloudflare-workers-and-pages]

Deploying repomix with    Cloudflare Pages

Latest commit:	7b127f8
Status:	✅  Deploy successful!
Preview URL:	https://632bd8ff.repomix.pages.dev
Branch Preview URL:	https://chore-npmignore-add.repomix.pages.dev

View logs

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request modifies the .npmignore file by adding two new entries to exclude specific directories from npm package publication. The website/ and .devcontainer/ directories are now explicitly ignored, which prevents these directories from being included when the package is packaged and published. Additionally, the package.json file's exports field is updated to provide a clearer structure for module exports, differentiating between ES module and CommonJS environments.

Changes

File	Change Summary
.npmignore	Added website/ and .devcontainer/ to the list of ignored directories
package.json	Updated exports field to include separate entries for import and require, both pointing to types and default exports

Note: No sequence diagram is generated for this change as it is a simple modification to the npm ignore configuration and an update to the export structure.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.26%. Comparing base (0815d25) to head (7b127f8).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #245   +/-   ##
=======================================
  Coverage   92.26%   92.26%           
=======================================
  Files          44       44           
  Lines        2108     2108           
  Branches      462      462           
=======================================
  Hits         1945     1945           
  Misses        163      163           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[standard-input]

No issues flagged.
Standard Input can make mistakes. Check important info.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

9-17: Consider future enhancements to the exports field.

While the current structure is solid, consider these future improvements:

1. Add Node.js version-specific conditions if needed (e.g., "node": ...)
2. Include development entry points if you plan to expose internal utilities for testing

Example structure:

 "exports": {
   ".": {
     "import": {
       "types": "./lib/index.d.ts",
+      "node": "./lib/index.node.js",
       "default": "./lib/index.js"
     },
     "require": {
       "types": "./lib/index.d.ts",
+      "node": "./lib/index.node.cjs",
       "default": "./lib/index.js"
     },
     "default": "./lib/index.js"
-  }
+  },
+  "./dev/*": "./lib/dev/*"
 }

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b4a2e00 and 7b127f8.

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

9-17: LGTM! Well-structured exports field.

The exports field is correctly configured to support both ES modules and CommonJS environments while maintaining proper TypeScript type definitions. The structure follows the Node.js package exports specification and properly handles the dual package hazard.