Skip to content

feat(build): add dev tunnel and tsdown path aliases#82

Merged
RedStar071 merged 2 commits into
mainfrom
feat/dev-tunnel-tsdown-improvements
Jun 19, 2026
Merged

feat(build): add dev tunnel and tsdown path aliases#82
RedStar071 merged 2 commits into
mainfrom
feat/dev-tunnel-tsdown-improvements

Conversation

@RedStar071

Copy link
Copy Markdown
Member

Summary

Improves local development and build tooling by adding an optional Cloudflare dev tunnel, filling in missing tsdown path aliases, aligning Prisma env loading with Staryl, and simplifying the Docker build stage.

Changes

  • Dev tunnel: Add untun and a tsdown plugin that starts a Cloudflare tunnel when --tunnel is passed or TUNNEL=1/TUNNEL=true is set. Uses HTTP_PORT (default 3000).
  • Tsdown aliases: Register #i18n and #utils resolvers so dev/build bundling matches runtime import paths.
  • Prisma config: Switch from dotenv to @wolfstar/env-utilities for env loading, consistent with Staryl.
  • Dockerfile: Remove redundant .npmrc copy from the dependency fetch stage.

Test plan

  • pnpm build succeeds
  • pnpm lint passes
  • TUNNEL=1 pnpm dev prints a tunnel URL after build
  • Docker image builds without the .npmrc copy step

Add optional Cloudflare tunnel via untun during dev builds, register
#i18n and #utils tsdown aliases, align prisma env loading with Staryl,
and drop redundant .npmrc copy from the Docker build stage.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@RedStar071, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 15 minutes and 39 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: bef66c68-bc62-4f45-a38b-3b6c3f06def9

📥 Commits

Reviewing files that changed from the base of the PR and between 3bbd480 and 963db23.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • .gitignore
  • Dockerfile
  • package.json
  • prisma.config.ts
  • tsdown.config.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/dev-tunnel-tsdown-improvements

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@RedStar071 RedStar071 merged commit 4cbede4 into main Jun 19, 2026
9 checks passed
@RedStar071 RedStar071 deleted the feat/dev-tunnel-tsdown-improvements branch June 19, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant