v0.4.0 | 23 Feb 2025

New features:

• Support for .html reloading
• Support for image asset reloading (<img>, favicon, etc)
• Server now watches sub-directories (recursive mode)
• Each page registers which files it wants to listen to and only receives those events, rather than ALL events
• Improved client-side logging

Fixes:

• Race-condition crashes

Other changes:

• Added Playwright tests
• Added prettier
• Now using ESModules on server
• reloader.js can now reload itself for easier debugging
• Tampermonkey script is part of project now, allowing for easier install
• README.md updated
• Updated package manager npm -> pnpm

Full Changelog: v0.3.1...v0.4.0

v0.3.1 | 7 May 2024

Oops! Things were a little broken 😬

Fixes:

• A bug where the PORT in window.location.origin was being replaced with undefined instead of an empty string

v0.3.0 | 29 Apr 2024

I've been using this project a lot more recently, and wanted to address some shortcomings.

New features:

• Works across the network! Watch changes happen live across multiple devices
• More verbose logging

Fixes:

• Changing the PORT env var now propagates to the injected reloader.js script (previously it required a manual change to override 3008)

Other changes:

• Web Hot Loader 🡒 Web Hot Reloader
• Removed outdated express dependency (what a throwback!)

Full Changelog: v0.2.0...v0.3.0

v0.2.0 | 9 Jul 2021

How would y'all like the ability to hot reload MULTIPLE CSS files in a single project?

Oh yeah!

v0.1.1 | 30 Dec 2020

This release contains a couple of updates on when/how websocket events get emitted:

• Debounce has been removed, ensure speedy reload times
• The contents of the CSS file are checked against their previous version (MD5 hash) to eliminate unnecessary duplicate events

v0.1.0 | MVP | 15 Jul 2020

Initial release, a bare-bones websocket-based hot reloader for CSS, without the need of any build tools or heavy-handed pipelines.

As a standalone application, it can be configured completely independent of your project, meaning no need to worry about keeping it out of your production code: it's never even there in development!