Release notes
CoolAdmin v3.5.0 dependency updates, measured asset savings, workflow fixes, compatibility, and verification.
Last updated October 13, 2026
CoolAdmin v3.5.0 — October 13, 2026
This release refreshes dependencies, reduces browser downloads, fixes development watching and chart cleanup, and adds reproducible build verification. It preserves all 35 pages and the no-build end-user workflow.
Dependency changes
| Dependency | Previous | Current |
|---|---|---|
| Vite | 8.2.0 | 8.3.4 |
| Sass | 1.102.0 | 1.105.1 |
| concurrently | 10.0.4 | 10.0.6 |
| FullCalendar | 7.0.2 | 7.1.2 |
| Terser | Not configured | 5.51.2 |
Chokidar 5.0.0, Pug 3.0.4, Bootstrap 5.3.8, Chart.js 4.5.1, Font Awesome 7.3.1, Hamburgers 1.2.1, and Leaflet 1.9.4 were already the latest stable npm releases checked on this date. The npm lockfile was refreshed. Prereleases were excluded.
Performance and runtime fixes
Chart.js now loads only on the five pages containing chart canvases. Removing it from 23 other pages avoids a 208,479-byte raw script request per affected page. The calendar bundles are minified from the installed FullCalendar package; upstream license banners and the MIT license are retained. Its two scripts shrink from 803,469 to 340,963 raw bytes, and from 164,748 to 95,797 gzip bytes. These measurements exclude CSS and are not page-load timings.
Dashboard refresh destroys charts before removing their canvases, releasing their observers and listeners. Repeated refreshes retain the expected instance count. Poppins uses font-display: swap so text can render while fonts load.
Workflow changes
The Pug watcher now watches a directory, filters .pug/.html files, debounces save bursts, and serializes builds. Identical output is not rewritten, preserving timestamps and avoiding unnecessary reloads. Compile errors leave the previous good output available while later fixes rebuild successfully.
npm run build:vendor reproduces calendar assets, npm test runs Node’s built-in test runner, and npm run check builds and tests. CI validates Node 22/24 and committed/generated asset consistency. The contributor minimum is Node >=22.12. Development sibling processes stop when one exits.
Verification
- Full production build and six Node regression tests passed.
- All 35 pages passed desktop/mobile Chromium checks at 1440 px and 390 px with zero console errors and failed requests.
- Month/week/day/list calendar views, new events, chart rendering, repeated dashboard refreshes, command palette, accent themes, and mobile navigation were exercised.
npm outdated: no outdated direct npm packages.npm audit: zero vulnerabilities on October 13, 2026.- Sass output remained unchanged except for the separately authored Poppins font-display declarations.
Compatibility and integration notes
Built files still run on static hosting with no Node runtime. FullCalendar’s core/theme filenames now end in .min.js under vendor/fullcalendar-7.1.2/; update custom integrations using the old paths. Use global UMD/script distributions with the template’s classic script tags.
The six theme presets change accent colors. Complete app dark-mode styling, backend authentication, persistent data, payments, and email require application work. Palette search is substring matching, and palette commands are maintained separately from Pug navigation data.
See deployment workflow for publication and rollback procedures.