Support JSR

[lambdalisue]

Summary by CodeRabbit

• New Features
  • Introduced GitHub Actions workflow for automated publishing on version tag pushes.
  • Updated README.md to support dynamic version resolution for Deno modules, enhancing flexibility in module version management.
• Documentation
  • Updated documentation to reflect new import path conventions and automated publishing steps.
• Refactor
  • Updated GitHub Actions to use the latest version of actions and added dry-run publishing step.
  • Revised package information and dependencies in deno.jsonc for better package management.
  • Streamlined import statements in scripts and tests for consistency and maintainability.

[coderabbitai]

Walkthrough

The project introduces a GitHub Actions workflow for Deno deployment, refines CI testing, and enhances module version management. It updates the workflow to support Deno, revises import paths for dynamic versioning, and modifies the package configuration and scripts for improved compatibility and efficiency. These changes streamline development and deployment processes, ensuring the codebase remains modern and maintainable.

Changes

Files	Change Summary
.github/workflows/jsr.yml	Adds a new workflow for Deno deployment on version-tagged pushes.
.github/workflows/test.yml	Updates checkout action version and adds a dry-run publishing step with Deno.
README.md	Updates TypeScript import paths for dynamic Deno module version resolution.
deno.jsonc	Updates package name, version, exports, and tasks; adds new imports.
scripts/build_npm.ts, unnullish_test.ts	Updates import statements for better module resolution and dependency management.

🐇✨
In the burrow of code, under the moon's soft glow,
A rabbit worked hard, with its paws tapping slow.
"To the future," it whispered, with eyes shining bright,
"We leap with these changes, into the night."
With each line and command, it danced with delight,
For the code was now ready, to take its first flight.
🌌🚀

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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/coderabbit-overrides.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.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2d0f3af and 57c629a.

Files selected for processing (6)

• .github/workflows/jsr.yml (1 hunks)
• .github/workflows/test.yml (2 hunks)
• README.md (4 hunks)
• deno.jsonc (1 hunks)
• scripts/build_npm.ts (1 hunks)
• unnullish_test.ts (1 hunks)

Additional comments not posted (7)

.github/workflows/jsr.yml (1)

26-27: Consider adding error handling or output validation for the publishing step to ensure successful execution.

deno.jsonc (1)

14-14: Consider adding documentation or comments explaining the $MODULE_VERSION placeholder used in imports for clarity and maintainability.

scripts/build_npm.ts (2)

1-1: LGTM! The update to more generic imports enhances maintainability.

---

1-1: Consider adding error handling for the file copy operations to ensure they complete successfully.

.github/workflows/test.yml (1)

42-44: Consider adding error handling for the JSR publish (dry-run) step to ensure it completes successfully and any issues are caught early.

unnullish_test.ts (1)

1-2: LGTM! Changing to local imports for assertEquals and unreachable enhances consistency and maintainability.

README.md (1)

27-27: Consider adding a brief explanation of the $MODULE_VERSION placeholder in the documentation to help users understand its purpose and usage.