chore: publish to jsr

[fengmk2]

Sweep Summary

Adds JSR (JavaScript Registry) configuration to publish the read-env-value package under the @eggjs namespace.

• Created jsr.json configuration file to enable publishing to JSR registry with the package name "@eggjs/read-env-value".
• Set up the package exports to point to the TypeScript source file directly, allowing TypeScript consumers to import types.

---

Ask Sweep AI questions about this PR

Summary by CodeRabbit

• Chores
  • Added a package configuration file specifying package details, version, license, and entry point.
  • Introduced a new automated workflow to streamline package publishing on code updates.

[coderabbitai]

Walkthrough

A new package configuration file, jsr.json, has been introduced. This file defines metadata for the @eggjs/read-env-value package, including its name, version, license, and the main export entry point. Additionally, a new GitHub Actions workflow named "Release to JSR" has been added, which triggers on pushes to the master branch and publishes the package using npx jsr publish. No changes to application logic or exported code entities are present.

Changes

File(s)	Change Summary
jsr.json	Added new package configuration file specifying package name, version, license, and export entry point.
.github/workflows/release-to-jsr.yml	Added new GitHub Actions workflow to publish the package on pushes to the master branch using npx jsr publish.

Poem

A new config file, crisp and neat,
Declares our package, small and sweet.
A workflow springs to life with cheer,
Publishing code when master’s near.
The rabbit hops, the setup’s done—
Now let the coding fun begun! 🐇✨

---

📜 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 68665a1 and be7023e.

📒 Files selected for processing (1)

• .github/workflows/release-to-jsr.yml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/release-to-jsr.yml

---

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

• 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.
• @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.

[fengmk2]

https://jsr.io/@eggjs/read-env-value

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/node-modules/read-env-value@3

commit: be7023e

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4109c32) to head (be7023e).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           31        31           
  Branches        16        16           
=========================================
  Hits            31        31           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

jsr.json (1)

1-7: Consider adding supplementary metadata.
To enhance package discoverability and documentation, you may include optional fields such as description, repository, keywords, and homepage.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ed90cce and 68665a1.

📒 Files selected for processing (1)

• jsr.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Node.js / Test (windows-latest, 20)
• GitHub Check: Node.js / Test (windows-latest, 22)

🔇 Additional comments (4)

jsr.json (4)

2-2: Verify package name consistency.
Ensure that @eggjs/read-env-value aligns with your organization and JSR registry naming conventions.

---

3-3: Confirm semantic versioning.
The version 1.0.0 follows SemVer rules. Please verify that this bump corresponds to your release strategy (major/minor/patch).

---

4-4: Validate license specification.
MIT is a permissive license—ensure that it matches your intended licensing and that a corresponding LICENSE file is present in the repo root.

---

5-5: Check exports field formatting.
Confirm that JSR’s schema accepts a string value for exports. If the spec requires an object (e.g., { ".": "./src/index.ts" }), please adjust accordingly.