Build and testing

Use the GitHub source repository for contributor work; it includes Pug, SCSS, scripts, and tests. End users can serve the committed HTML without Node.

npm ci
npm run dev
npm run check

npm run check runs the production build and all six tests. npm test uses Node’s built-in test runner; files are named test/*.test.js. No coverage threshold or formatter/linter is configured.

What is tested

• Local HTML/CSS assets and linked page destinations exist.
• Chart.js loads exactly on pages containing chart canvases.
• Calendar paths and the minified bundle match the installed FullCalendar version.
• Pug builds preserve unchanged timestamps and report compilation errors.
• Directory watching detects changes, added pages, and deleted includes, then recovers when the include is restored.
• Repeated dashboard refresh destroys old chart instances before replacing canvases and preserves unrelated charts.

Tests use temporary fixtures and clean them up. On restricted macOS environments, filesystem watching may require normal native filesystem access.

Build commands

Command	Result
npm run build	Vendor calendar assets, Pug HTML, and Sass CSS
npm run build:vendor	Minified FullCalendar scripts, CSS, and license
npm run build:pug	Root HTML pages
npm run build:sass	css/theme.css and css/app.css

Commit generated outputs with source changes. CI installs the lockfile on Node 22/24, runs the checks, and rejects modified or missing generated assets. Vite is the dev server, not the production builder.

Browser verification

Check desktop/mobile layouts, console errors, and failed requests. Exercise calendar Month/Week/Day/List views, chart rendering, dashboard refresh, palette keyboard navigation, accent presets, and mobile navigation after shared changes.

For v3.5.0 all 35 pages passed Chromium checks at 1440 px and 390 px. The build and six tests passed, npm audit reported zero vulnerabilities, and npm outdated reported no outdated direct npm packages on October 13, 2026. These checks do not establish Lighthouse scores, full cross-browser coverage, or backend integration behavior.