node v8.9.4, with pnpm
Installing...
ERROR Unexpected token / in JSON at position 0
at parse
at at /home/nvm/pnpm/lib/node_mo… …server/lib/connectStoreController.js:69
at throw
at rejected …/server/lib/connectStoreController.js:5
at _tickCallback internal/process/next_tick.js:188
Looks like your package.json is valid, so pnpm is probably trying to parse something as JSON that isn’t actually JSON. Unfortunately, I’m not sure what exactly that might be.
Try to refresh your project from the console,
also try to remix the project and see if the new one works,
if still doesn’t then the problem may be related to your browser and as far as I know refreshing the page will show what’s wrong, sometimes losing connection hides a part of the code, especially when pasting.
Doing that gave me these errors, which I believe are the cause.
node v8.9.4, npm 5.6.0
Installing...
npm WARN deprecated libcipm@1.6.3: This version mistakenly dropped node@4 compatibility in a semver-patch release. Please stay on 1.6.2 or update to 2 or latest
npm WARN deprecated npm-registry-fetch@1.1.1: this version has a breaking change. use 1.1.0 or upgrade to latest
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
Ignore them, just deprecated packages
update your packages if you want to get rid of them, they might be the dependencies of the packages themselves which only their authors can update.
Edit: let it finish installing first and it’ll be fine.
It came back about 10 hours ago. People told me that it’s glitch’s internet connection. Could this be because of the recent problems with glitch’s outage and it being slow? Both have been fixed and it seems fine now.
It’s possible that Glitch is the problem, but that doesn’t seem very likely. If you add .catch() blocks to your promise handling, you should be able to get a better error message.
The error isn’t helping me much. This is only happening to my bussiest project so I’m probably going to try a paid host and see how it does. Will stick to glitch with my other ones
Confirmed. This issue is because there’s not enough ram. I monitored the ram on my paid host and once it got to 95-100% the CPU started spiking and the error appeared. I upgraded the ram and it works fine again.