bot-implementer 37f2c9a2f2 chore: use default test discovery so npm test works across node builds
`node --test <dir>` treats a directory argument as a module path on some
Node builds (reproduced on v22.23.2), so `npm test` failed before running
any tests. `node --test` with no args discovers the same tests/ files
portably.
2026-08-25 12:30:06 +00:00

Personal Blog

A small static personal blog. No build step, no backend — plain HTML, CSS, and vanilla JavaScript.

Pages

  • index.html — home page
  • contact.html — contact page (opens the visitor's mail client with the form fields pre-filled via a mailto: link)

Development

Serve the directory with any static file server, e.g.:

python3 -m http.server 8000

Then open http://localhost:8000.

Tests

Tests use Node's built-in test runner (no dependencies to install):

npm test

Project layout

index.html        Home page
contact.html      Contact page
css/style.css     Global + responsive styles
js/mailto.js      Pure mailto: URL builder (unit tested)
js/contact.js     Contact form wiring (browser + tests)
tests/            Node built-in test suite
.gitea/workflows/ ci.yml runs `npm test` on PRs and pushes to main
S
Description
No description provided
Readme
857 KiB
Languages
JavaScript 89%
TypeScript 9.9%
Dockerfile 1.1%