fix: export sendmessage function

[fengmk2]

Summary by CodeRabbit

• New Features
  • Introduced a new export for the sendmessage function in the main module.
• Bug Fixes
  • Updated import statements for the sendmessage function in test files to use a new alias.
• Chores
  • Updated Node.js version specification in CI configuration.
  • Added package-lock.json to the .gitignore file.
  • Updated various dependencies in package.json.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes several updates across multiple files. The Node.js version specification in the GitHub Actions workflow has been modified to include version '16'. The .gitignore file now ignores package-lock.json. Import statements for the sendmessage module in master.js and worker.js have been changed from default to named imports. The package.json file has updates to various dependencies and the addition of a module field. A new export for the sendmessage function has been added in src/index.ts, and the test file has been updated to use an alias for the sendmessage function.

Changes

File	Change Summary
.github/workflows/nodejs.yml	Updated Node.js version specification from '18.19.0, 18, 20, 22' to '16, 18.19.0, 18, 20, 22'.
.gitignore	Added package-lock.json to the list of files to be ignored by Git.
README.md	Changed import statements in master.js and worker.js from default to named imports for sendmessage.
package.json	Updated dependencies: @arethetypeswrong/cli, @types/node, eslint-config-egg, mocha, tshy. Added module field and removed source from exports.
src/index.ts	Added export for sendmessage function.
test/sendmessage.test.js	Modified import statement to include alias sendmessage2 for sendmessage.

Possibly related PRs

• feat: support cjs and esm both by tshy #6: The changes in the .github/workflows/nodejs.yml file in both PRs involve updating the Node.js version specifications, indicating a direct relationship in the context of CI configuration.

Poem

🐇 In the land of code, we hop with glee,
New versions and imports, as fresh as can be.
With sendmessage now shining bright,
Our tests and builds take flight!
Ignore the locks, let the versions flow,
In our coding burrow, watch our project grow! 🌱

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 618ed26 and a43a5d6.

📒 Files selected for processing (6)

• .github/workflows/nodejs.yml (1 hunks)
• .gitignore (1 hunks)
• README.md (2 hunks)
• package.json (2 hunks)
• src/index.ts (1 hunks)
• test/sendmessage.test.js (2 hunks)

---

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. (Experiment)
• @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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@arethetypeswrong/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+47	31.2 MB	andrewbranch
npm/@types/[email protected]	None	+1	2.37 MB	types
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+166	18.3 MB	fengmk2
npm/[email protected]	environment, eval, filesystem Transitive: shell	+88	8.19 MB	joshuakgoldberg, uzlopak, voxpelli
npm/[email protected]	environment, filesystem, shell Transitive: unsafe	+56	4.96 MB	isaacs

🚮 Removed packages: npm/@arethetypeswrong/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.22%. Comparing base (30acc65) to head (a43a5d6).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
+ Coverage   97.14%   97.22%   +0.07%     
==========================================
  Files           1        1              
  Lines          70       72       +2     
  Branches       16       16              
==========================================
+ Hits           68       70       +2     
  Misses          2        2              

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