hi, thanks for the follow up && sure sure, thanks for reminding me about the time/size limits. looking more at the logs it looks like my app could not start because a npm module could not be found
firstname.lastname@example.org dev:start /app
sh: 1: react-scripts: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! email@example.com dev:start:
npm ERR! spawn ENOENT
npm ERR! Failed at the firstname.lastname@example.org dev:start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npm-cache/10.15.0/_logs/2019-01-26T03_17_14_696Z-debug.log
i mention the disk space thing because i saw a warning in the container stats about disk usage and using the console noticed the filesystem was, indeed, full. are there more logs a glitch admin might be able to see to help understand why this happened? and if there’s anything i can do to avoid such? i’m not sure why the npm module stopped being there unless for some reason the container/project was re-built? i’m not sure why the contents of
node_modules/ would change, otherwise?
also, by stop working i mean: the project would not load because the start script failed because of the missing npm module, so page didn’t load and eventually gave a 500 error.