Build logs, code tinkering, and tool recommendations.
View all tags
A brand-new Windows machine, a fresh terminal, npm -v, and this happens:
'npm' is not recognized as an internal or external command,
operable program or batch file.
Your command is fine. The machine is fine. Windows simply does not ship with Node.js, npm or Git.
This post starts from why the command fails and ends with a verified environment. No prior knowledge assumed.
This site is Docusaurus on Cloudflare Pages. Deploying it is not the hard part. The hard part is everything after: caching, response headers, 404s, bilingual sitemaps, absolute paths leaking into the bundle, and the two or three Cloudflare edge features that fight with your framework.
This post walks the whole path, and ends with a checklist you can run through line by line.
← swipe horizontally to see the full diagram →
The build runs on Cloudflare's machines. You need neither a server nor an upload of build/.
With seventeen posts, two default pagination spots started to feel thin:
The symptom: on a phone, open “Start here” from the homepage, then tap the hamburger — the menu shows only the docs navigation. Blog and Tools are gone.
I assumed my own changes had broken the navbar. Reading the framework source showed otherwise: this is Docusaurus’s design.
The interesting question about adding security badges is not which one looks best, but whether to use a third-party “seal” or build your own.
I chose the latter, and the reason is verifiability.
The obvious doubt about a browser-based PDF tool is whether it can work without uploading anything.
It can. PDF is a structured container format; pages can be copied into a new document without ever rendering them. But a few limits need stating up front, or users hit a wall exactly when it matters.
Two of the new tools have to produce files from nothing: one packs PNGs into a .ico, the other packs text into a .zip.
The usual move is to install a library for each. But both formats are less complicated than their reputation suggests.
A QR tool looks like the simplest thing: type text, draw black and white squares. Building it, I hit one pitfall choosing a library and another handling Chinese text.
The site is deployed on Cloudflare Pages, and the build command is just npm run build. The longer I use it, the clearer it is that static hosting is not "upload and forget" — a few details directly affect the result.
I wanted to drop screenshots straight into posts without watching the repository get fatter every week. So the site got an object store — and I ended up thinking the whole hotlinking question through.
"The footer looks off — asymmetric on desktop, left-hugging and a bit plain on mobile." Before changing anything I took screenshots and measured, and "doesn't look good" turned out to be five concrete problems.
The scariest part of mobile support is "looks fine to me". I started with my eyes and screenshots, and missed several problems that only appear at real device widths. Then I switched to measuring with a headless browser — and found that screenshots themselves can lie.