Before your first deploy: checks to paste into Claude Code
Paste the prompt below into Claude Code before you publish. It runs eight checks, fixes what it can and reports back. When all pass, one command takes your site live on a free HTTPS link.
Last updated: 21 October 2026.
The 8 checks
- The build runs. Run the build (npm run build or the project's own build command) and fix every error. Tell me which folder it writes: dist, build or out.
- No secrets in the files. Search the built folder and the repo for .env files, API keys, passwords and secret keys. Nothing secret may end up in the folder I publish. Public keys meant for the browser are fine; list them.
- Env vars are set. List every environment variable the code reads. Confirm each one has a value in the build, and that the site does not break when one is missing.
- Relative asset paths. Check that scripts, styles, images and fonts use paths that work on any address (/assets/... or ./assets/...), not C:\, /Users/ or localhost. Check that file names match in capital letters.
- Unknown pages. Open an address that does not exist, like /does-not-exist. DropTheHassle serves your index.html for any address it has no file for, so a 404.html is not used. If the site has a client-side router, add a catch-all route that shows a clear 'page not found' message with a link home. It must never be a blank page.
- Title, description, favicon. Every page has a real <title>, a meta description of one sentence and a favicon. No 'Vite + React' or 'Untitled'.
- Links work. Click through every link and button. Fix links that point to #, localhost or a page that is not there. Check that mailto: and phone links are right.
- Mobile. Check the page at 375 px wide: a viewport meta tag, no sideways scrolling, text you can read, buttons you can tap.
The prompt to paste
Before I deploy, go through these checks one by one. Fix what you can, and give me a short report: pass or fixed per check.
1. The build runs: Run the build (npm run build or the project's own build command) and fix every error. Tell me which folder it writes: dist, build or out.
2. No secrets in the files: Search the built folder and the repo for .env files, API keys, passwords and secret keys. Nothing secret may end up in the folder I publish. Public keys meant for the browser are fine; list them.
3. Env vars are set: List every environment variable the code reads. Confirm each one has a value in the build, and that the site does not break when one is missing.
4. Relative asset paths: Check that scripts, styles, images and fonts use paths that work on any address (/assets/... or ./assets/...), not C:\, /Users/ or localhost. Check that file names match in capital letters.
5. Unknown pages: Open an address that does not exist, like /does-not-exist. DropTheHassle serves your index.html for any address it has no file for, so a 404.html is not used. If the site has a client-side router, add a catch-all route that shows a clear 'page not found' message with a link home. It must never be a blank page.
6. Title, description, favicon: Every page has a real <title>, a meta description of one sentence and a favicon. No 'Vite + React' or 'Untitled'.
7. Links work: Click through every link and button. Fix links that point to #, localhost or a page that is not there. Check that mailto: and phone links are right.
8. Mobile: Check the page at 375 px wide: a viewport meta tag, no sideways scrolling, text you can read, buttons you can tap.
When all pass, run: npx -y dropthehassle@latest deploy .Go live
In the project folder, after the build:
npx -y dropthehassle@latest deploy .Your site goes live on a free HTTPS link, yourname.dropthehassle.app, with no account. Claim it to keep it, then add your own domain when you want. Something still blank? See why a site works locally but not online.
Questions
Do I need an account for the first deploy?
No. The first deploy goes live on a free HTTPS link, yourname.dropthehassle.app, with no account and no card. Claim it to keep it.
What if a check fails after I go live?
Fix it in Claude Code, build again and deploy again. The site stays live until the new one is on.
Can I use my own domain?
Yes. A .com bought here is €19 / $19 a year, including VAT in the EU, with no DNS edit. A domain you already own needs one A record.