Wanted to test the new server-side debugger with one of my projects (https://animated-pixel-gradients.glitch.me) but I’m getting repeated errors in the log:
> firstname.lastname@example.org build /app > build-if-changed Starting inspector on localhost:9200 failed: address not available npm ERR! code ELIFECYCLE npm ERR! errno 12 npm ERR! email@example.com build: `build-if-changed` npm ERR! Exit status 12 npm ERR! npm ERR! Failed at the firstname.lastname@example.org build 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! /tmp/npm-cache/8.10.0/_logs/2018-03-28T16_19_11_273Z-debug.log 🐞 The debugger could not be started. See https://glitch.com/faq#debugger
I checked https://glitch.com/faq#debugger and found these requirements, which I believe my project fulfills.
There are a couple of requirements: It only works with Google Chrome, you need to be using Node 8.x or above, and using
- Using Google Chrome
- Using Node 8.10.0
- I’m using
process.env.PORTfor launching the Express app
- Source maps only apply to my client-side code
- No parallel Node processes
The error message sounds like a port error, but I don’t see what I’m doing wrong.