Skip to content

fix(site): correct canonical URLs and dev CSS build - #189

Open
jeremymcs wants to merge 2 commits into
mainfrom
jeremymcs/website
Open

fix(site): correct canonical URLs and dev CSS build#189
jeremymcs wants to merge 2 commits into
mainfrom
jeremymcs/website

Conversation

@jeremymcs

Copy link
Copy Markdown
Owner

Follow-up to #187, which merged before these two fixes were pushed. Both are on the same branch.

1. Canonical URLs pointed at a domain we do not own — please prioritise this one

The placeholder https://patchdeck.vercel.app shipped to main in #187. That hostname is not ours: it serves an unrelated project titled "PatchDeck — Visual Network Designer". Vercel assigned this project patchdeck-eta.vercel.app precisely because the plain name was already taken.

Left in place, it hands our canonical signal, OG link previews and sitemap to a third party's site. Eight references were affected:

  • index.html<link rel="canonical">, og:url, og:image, twitter:image, and the JSON-LD url
  • public/robots.txt — the Sitemap: line
  • public/sitemap.xml — the <loc> element

All now point at https://patchdeck-eta.vercel.app. site/README.md records why the plain hostname must not be substituted back.

Production is currently serving the incorrect canonical, so this is worth merging promptly.

2. Dev server served the page with no stylesheet

build.mjs --watch cleared dist/ and then relied on the Tailwind watcher to recreate styles.css, but the Tailwind CLI exits the moment stdin reaches EOF — which is what it gets when the process runs detached. Result: styles.css 404'd and the page rendered unstyled.

  • run a one-shot CSS build before starting the watcher, so styles.css always exists regardless of whether the watcher survives
  • give the watcher an open stdin pipe rather than an inherited or ignored one
  • log when the watcher exits instead of failing silently

The one-shot npm run build path used by CI and Vercel was never affected.

Also pins framework, buildCommand, outputDirectory and installCommand in vercel.json, so deployments do not depend on dashboard auto-detection.

Verification

Vercel project patchdeck is created and linked (root directory site). Verified against the live branch preview at patchdeck-git-jeremymcs-website-fluxlabs-projects.vercel.app:

  • page, styles.css, all six screenshots, favicon.svg, robots.txt, sitemap.xml and og.png all return 200 with correct content types
  • cache-control: public, max-age=31536000, immutable confirmed on /assets/*
  • x-content-type-options, x-frame-options, referrer-policy and permissions-policy confirmed on all routes
  • rendered in a real browser, no console errors

🤖 Generated with Claude Code

https://claude.ai/code/session_01LF9K9Y3sGMA2EAQVqF93JW

build.mjs --watch cleared dist/ and then relied on the Tailwind watcher to
recreate styles.css, but the Tailwind CLI exits as soon as stdin reaches
EOF — which is what it gets when the process runs detached. The dev server
served the page with no stylesheet at all.

- run a one-shot CSS build before starting the watcher so styles.css always
  exists, independent of whether the watcher survives
- give the watcher an open stdin pipe rather than an inherited or ignored one
- log when the watcher exits instead of failing silently

The one-shot `npm run build` path used by CI and Vercel was unaffected.

Also pins framework, build command, output directory and install command in
vercel.json so the deployment does not depend on dashboard auto-detection.
The placeholder canonical, og:url, og:image, twitter:image, JSON-LD url,
robots.txt sitemap line and sitemap.xml loc all pointed at
patchdeck.vercel.app. That hostname is not ours: it serves an unrelated
project called "PatchDeck — Visual Network Designer". Vercel assigned this
project patchdeck-eta.vercel.app precisely because the plain name was taken.

Left as-is it would have handed our canonical signal and link previews to a
third party's site. Updates all eight references and records why the plain
hostname must not be used.
@vercel

vercel Bot commented Aug 30, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
patchdeck Ready Ready Preview Aug 30, 2026 5:44pm

Request Review

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