Got similar issue, replaced

!production && livereload('public'),

with this instead to make it work

!production && livereload({ watch: 'public' }),

What browsers are people using?

I find that @leek9's solution improves behaviour in Chrome but not Firefox Developer Edition.

Hi 👋🏻,

Livereload seems to stop after the first change. Upon research, it seems there's a similar issue on the main rollup GitHub repository.

This bug manifests on Windows 10 / WSL 2. I'll be sending a PR in a moment.

Your PR did the trick for me. Works fine on arch linux with firefox and chromium.

What browsers are people using?

I find that @leek9's solution improves behaviour in Chrome but not Firefox Developer Edition.

For me it the other way around. Chrome does not work Firefox does. But I am not sure If that problem happend in Firefox.

What browsers are people using?
I find that @leek9's solution improves behaviour in Chrome but not Firefox Developer Edition.

For me it the other way around. Chrome does not work Firefox does. But I am not sure If that problem happend in Firefox.

I'm pretty sure this is a browser-independent problem.

Using WSL 2 with docker containers

Deleting my node_modules in my project, and deleting rollup in my C:\Program Files\nodejs\node_modules global folder and force reinstalling with npm i -g rollup --force worked for me.

For those who use vim and experience this issue, this blog post might have some pointers for a solution https://lee-phillips.org/badvim/