fix: replace hardcoded npmx.dev & docs.npmx.dev with env-specific URLs

[serhalp]

Extract a composable that returns URLs for this app itself (and docs, which lives in this codebase), so that URLs are always internally consistent within an environment, e.g. in dev links go to dev.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 12, 2026 0:54am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored		Feb 12, 2026 0:54am
npmx-lunaria	Ignored		Feb 12, 2026 0:54am

[codecov]

Codecov Report

❌ Patch coverage is 57.14286% with 6 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
app/app.vue	0.00%	2 Missing ⚠️
app/components/Package/SkillsModal.vue	0.00%	1 Missing and 1 partial ⚠️
app/composables/useJsonLd.ts	0.00%	1 Missing ⚠️
app/pages/package/[[org]]/[name].vue	0.00%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request centralises URL configuration by introducing a new useAppUrls() composable that provides dynamic site and documentation URLs. Hard-coded URLs across multiple components and pages are replaced with calls to this new composable. The createWebSiteSchema() function signature is updated to accept a siteUrl parameter. Environment configuration is extended to expose siteUrl through the application configuration via getEnv(). Constants are renamed from NPMX_SITE to NPMX_SITE_PROD and a new NPMX_DOCS_SITE_PROD constant is added to shared utilities.

Possibly related PRs

• chore: use getEnv environment abstraction in lunaria module #1146: Modifies config/env API by adding getSiteUrl and siteUrl to getEnv's return, creating a direct code-level dependency on the configuration changes introduced here.
• chore: use getEnv in oauth module for platform agnosticity #1148: Both PRs modify config/env and extend getEnv's return shape to expose environment-specific URLs.
• refactor: add proper route segments for package code #1301: Both PRs modify canonical URL construction logic on the package-code page, with this PR injecting configurable siteUrl values.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description accurately describes the changeset: extracting a composable for environment-specific URLs to replace hardcoded site references.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/per-env-self-urls

---

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[knowler]

wondering if we should or should not hardcode this? It is possible to pass flags with the dev command to change the port/host. Could we get that from somewhere else?

[danielroe]

unfortunately only 127.0.0.1 works for the atproto oauth callback

but yes, you can get the actual host and port in module space

[serhalp]

as I have a feature PR stacked on this one and PRs get stale fast here 😅 and this PR leaves things no worse than before, how would you feel about following up on this later?

[sacrosanctic]

https://vercel.com/docs/deployments/generated-urls#generated-from-git

the URL's are deterministic, so can we just construct them during the build?

[serhalp]

as I have a feature PR stacked on this one and PRs get stale fast here 😅 and this PR leaves things no worse than before, how would you feel about following up on this later?