Rename tenedev

[tenedev]

Summary by CodeRabbit

• New Features

  • Export metadata now includes direct source links for easier navigation.
  • Project generation prompts for a display name and uses it in package metadata and documentation paths.

• Documentation

  • Added browser usage guidance for juk-web.
  • Improved juk-cli overview, badges, and usage descriptions.
  • Updated package descriptions and contribution guidance.

• Maintenance

  • Updated repository, support, issue-tracking, and automation links.
  • Removed obsolete package publishing configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5a18fff

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[tenedev]

@coderabbitai title

[coderabbitai]

Warning

Review limit reached

@tenedev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2afda3a7-142e-4f5d-9847-54ba3fbac06c

📥 Commits

Reviewing files that changed from the base of the PR and between 77ef96c and 5a18fff.

📒 Files selected for processing (1)

• packages/js-utils-kit/README.md

📝 Walkthrough

Walkthrough

The change updates repository ownership references, GitHub and package metadata, contributor documentation, package READMEs, export source metadata, and project generation prompts.

Changes

Repository alignment and documentation

Layer / File(s)	Summary
Repository metadata and GitHub configuration .changeset/config.json, .github/..., README.md, package.json, renovate.json	Repository ownership, sponsorship, issue assignments, links, package metadata, changelog settings, and Renovate settings now use tenedev.
Contributor and package documentation CONTRIBUTING.md, packages/*/README.md	Contributor guidance now references pnpm, Turbo, and Biome. Package READMEs include updated descriptions and usage documentation.

Tooling enhancements

Layer / File(s)	Summary
Export metadata and project generation scripts/exports.js, exports.json, scripts/new-project.js	Exports now include declaration source URLs. Project generation validates a display name and writes it to package metadata and homepage paths.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Developer
  participant newProject as new-project.js
  participant PackageJson as generated package.json
  participant Homepage
  Developer->>newProject: Enter and validate display name
  newProject->>PackageJson: Write displayName metadata
  newProject->>Homepage: Set /modules/displayName path

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the repository owner rename from teneplaysofficial to tenedev.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rename-tenedev

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail
gh pr view 266 --repo tenedev/js-utils-kit --json number,title,url --jq '{number, title, url}'

Length of output: 360

---

@tenedev The title is Rename tenedev. It matches the PR objective.

_{You are interacting with an AI system.}

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Line 23: Remove the stale ESLint entry from the tooling list in
CONTRIBUTING.md, while retaining Biome and the existing tooling guidance so
contributors see only the active linter.

In `@packages/js-utils-kit/README.md`:
- Line 3: Update the README subtitle to complete the phrase after “type-safe”
with an appropriate noun, such as “utilities” or “APIs,” while preserving the
existing meaning.

In `@scripts/new-project.js`:
- Around line 92-95: Update the validate callback for the display-name prompt to
validate the trimmed value rather than the original input, so whitespace-only
names are rejected; preserve the existing non-empty error message and ensure the
accepted value remains compatible with the later displayName.trim() metadata
generation.
- Around line 27-36: Update buildPackageJson so the homepage URL encodes
displayName as a single path segment when constructing the homepage value, while
preserving the original displayName unchanged in pkg.displayName.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dc3e1ecf-2f17-4a34-9935-5f6640ccfbca

📥 Commits

Reviewing files that changed from the base of the PR and between 0ddc452 and e66f26d.

📒 Files selected for processing (15)

• .changeset/config.json
• .github/FUNDING.yml
• .github/ISSUE_TEMPLATE/bug-report.yml
• .github/ISSUE_TEMPLATE/config.yml
• .github/ISSUE_TEMPLATE/utility-proposal.yml
• CONTRIBUTING.md
• README.md
• jsr.json
• package.json
• packages/js-utils-kit/README.md
• packages/juk-cli/README.md
• packages/juk-web/README.md
• renovate.json
• scripts/exports.js
• scripts/new-project.js

💤 Files with no reviewable changes (1)

• jsr.json