Add more fields to the deno file

[w3nl]

Summary by CodeRabbit

• Chores
  • Updated package metadata with a new name, version, and license for clearer identification and licensing transparency.
  • Defined the module entry point to improve import resolution and tooling compatibility.
  • No functional changes to runtime behavior.

[coderabbitai]

Walkthrough

Added metadata fields to deno.json: name "@trojs/validator", version "11.1.2", license "MIT", and exports "./src/validator.js". No source code changes.

Changes

Cohort / File(s)	Summary of changes
Configuration `deno.json`	Added fields: `name`, `version`, `license`, `exports` pointing to `./src/validator.js`.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I stamped my paws on JSON ground,
Named the bundle, versioned sound;
A license pinned, exports aligned—
Paths now clear, neatly defined.
Hippity-hop, configs in sight,
Ship it swift, the carrots are light! 🥕✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/node-24.x-lockfile

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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

🧹 Nitpick comments (1)

deno.json (1)

5-5: Future-proof exports with an object map (optional).

If you expect subpath entrypoints later, switch to an object now.

Apply:

-    "exports": "./src/validator.js",
+    "exports": {
+        ".": "./src/validator.js"
+    },

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2f83773 and 4e415ca.

📒 Files selected for processing (1)

• deno.json (1 hunks)

🔇 Additional comments (3)

deno.json (3)

2-5: JSR metadata addition looks good.

Scoped name, semver version, SPDX license, and a single-string exports entry are valid for deno.json used with JSR. No functional concerns from these additions.

---

5-5: ESM entrypoint verified
src/validator.js exists and exports named members Validator and types.

---

2-4: No changes needed: version and license are consistent across deno.json and package.json.