Support JSR

[lambdalisue]

Summary by CodeRabbit

• New Features
  • Updated functionality to include new badges for jsr and denoland.
  • Restructured Promise.all calls for rlock and lock methods.
• Documentation
  • Updated README with new badges and project status information.
• Chores
  • Implemented import statement modifications for better code organization.

[coderabbitai]

Walkthrough

The project has been updated to include new badges for jsr and denoland in the README, along with restructuring Promise.all calls for rlock and lock methods. Additionally, the WaitOptions import statement in queue.ts and stack.ts has been modified for consistency.

Changes

File(s)	Change Summary
README.md	Updates badges and restructures Promise.all calls.
queue.ts	Modifies the WaitOptions import statement for consistency.
stack.ts	Modifies the WaitOptions import statement for consistency.

🐰✨
Amongst the code's dance, where bugs and fixes play,
New badges gleam bright, in the README's array.
WaitOptions now consistent, in queue and in stack,
Our codebase evolves, on the right track.
🌟📚🔧

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 f61dbcb and e7032ac.

Files selected for processing (4)

• .github/workflows/jsr.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)
• README.md (2 hunks)
• deno.jsonc (1 hunks)

Additional comments not posted (5)

.github/workflows/jsr.yml (1)

1-27: Ensure the jsr:@david/publish-on-tag@0.1.3 script is compatible with the project's requirements for JSR support and that it adheres to security best practices.

deno.jsonc (1)

3-5: Confirm the version 0.0.0 of @lambdalisue/async is intended. Typically, a more stable version is used in production.

.github/workflows/test.yml (1)

41-43: The addition of the "JSR publish (dry-run)" step is a good practice for safely testing the publish process. Ensure that this step is correctly integrated into the CI/CD pipeline and does not interfere with other steps.

README.md (2)

3-4: Ensure the URLs for the jsr and denoland badges are correct and lead to the intended destinations. This helps users and contributors quickly assess the project's status and compatibility.

---

91-108: The restructuring of Promise.all calls for rlock and lock methods appears to improve code readability and concurrency handling. Review the changes to ensure they align with the project's standards for asynchronous operations.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between e7032ac and 93d5376.

Files selected for processing (3)

• README.md (2 hunks)
• queue.ts (1 hunks)
• stack.ts (1 hunks)

Additional comments not posted (4)

stack.ts (1)

1-1: LGTM! Importing WaitOptions as a type is a good practice for tree shaking and reducing bundle size.

queue.ts (1)

1-1: LGTM! Importing WaitOptions as a type is consistent with best practices for optimizing the code.

README.md (2)

3-4: The addition of jsr and denoland badges enhances the documentation. Please ensure the URLs are correct and functional.

---

91-108: Ensure the restructuring of Promise.all calls for rlock and lock methods maintains the intended logic and does not introduce side effects.