`rollup -c -w` exits without any error.

I have some new data, so I thought I’d gather the relevant issues here.

Even worst for me with svelte template: command exit (rollup -c -w) without any error. Removing livereload from the config solve the issue: command works fine. I was wondering if it was only me but seems like I’m not alone: https://github.com/sveltejs/template/issues/133 _Originally posted by @sansnom in https://github.com/thgh/rollup-plugin-livereload/issues/46#issuecomment-645471396_

I’ve had this issue sometimes and just now I found that I accidentally had another terminal with rollup -c -w running in the same working directory.

So somehow the watching AND livereload plugin has a problem.

With one running instance with watch and livereload, the second instance…

• rollup build: works OK.
• rollup watch, livereload not called: works OK.
• rollup watch with livereload enabled: silently exits. <-- our issue

[avimar]

Oh! Figured it out, I think. It seems livereload always binds to port 35729. It’s running into a port conflict.

I ran into the same issue when I had rollup with livereload in two different work directories.

So we can launch an instance on a different port - https://github.com/thgh/rollup-plugin-livereload/blob/1bbcf8f2ea20c2adf554317b0c00b8355d7aaaca/src/index.js#L22

e.g. !production && livereload({watch: 'public', port: 35730}),

Not sure the best way to proceed - try to launch and try again with a new port? Always pass a random port? Possibly other options.

[avimar]

Nice catch ! On Windows, the port is taken by “Intel® Active Management Technology Local Manageability Service” (LMS.exe).

Oh wow, for me on windows 10, it was only taken when I was running a live reload in another cli.

Regardless, we have a port usage issue.