Crashing when saving rollu.config.js
See original GitHub issueDescribe the bug When you press ctrl+s, without changing anything, the application crashes
Logs
{ Error: listen EADDRINUSE: address already in use :::35729
at Server.setupListenHandle [as _listen2] (net.js:1279:14)
at listenInCluster (net.js:1327:12)
at Server.listen (net.js:1414:7)
at Server.listen (/home/gabriel/Workspace/my-svelte-project/node_modules/livereload/lib/livereload.js:80:28)
at Object.exports.createServer (/home/gabriel/Workspace/my-svelte-project/node_modules/livereload/lib/livereload.js:246:14)
at livereload (/home/gabriel/Workspace/my-svelte-project/node_modules/rollup-plugin-livereload/dist/index.cjs.js:19:29)
at Object.<anonymous> (/home/gabriel/Workspace/my-svelte-project/rollup.config.js:48:20)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.require.extensions..js (/home/gabriel/Workspace/my-svelte-project/node_modules/rollup/dist/bin/rollup:838:24)
at Module.load (internal/modules/cjs/loader.js:653:32)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 35729 }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! svelte-app@1.0.0 autobuild: `rollup -c -w`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the svelte-app@1.0.0 autobuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gabriel/.npm/_logs/2019-09-07T19_44_19_736Z-debug.log
ERROR: "autobuild" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! svelte-app@1.0.0 dev: `run-p start:dev autobuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the svelte-app@1.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gabriel/.npm/_logs/2019-09-07T19_44_19_778Z-debug.log
To Reproduce
npx degit sveltejs/template my-svelte-project
cd my-svelte-project
npm install
npm run dev
Open rollup.config.js and press ctrl+s
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Problem with rollup dev server crashing in svelte 3
I suspect this is caused by the plugin rollup-plugin-livereload which attempts to watch the public folder for changes. There are too many files ......
Read more >How to Bundle JavaScript With Rollup — Step-by-Step Tutorial
Step 1: Install Rollup and create a configuration file. To get started, install Rollup with the following command: npm install --save-dev rollup. Next ......
Read more >Jenkins crashing while saving the global system configuration
Getting below exception while adding the ssh server in publish-over-ssh plugin. Test connection is successful. But apply/save giving below error.
Read more >Console crashes after you upgrade to Configuration Manager ...
The Configuration Manager console crashes after you update to Configuration Manager current branch, version 2107.
Read more >ArcMap crashes when saving an existing project
I had this problem, but it was because I was using a third party extension that has expired. Once I turned off the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gargleblaster Like I said, bug in rollup-plugin-livereload. Already reported.
I’ve sent a PR to rollup-plugin-livereload.
I’ve also made a “dist” branch of the fix in the PR, that you can use while waiting for the merge (build files are excluded in normal branch).
For example:
I’ve also pushed an example using this, on a branch of my live template. You can try it to see if the fix is working for you…
@rixo This doesn’t seem to fix the issue. I’ve tried your branch and the error keeps the same