Ok well you’ve resolved the disk space issue, so that’s a start.
&& node /app/server.js to your start script to try to get your project to start up fully, but never fully starts due to errors in your /app/server.js file. Because of those errors it never gets to the line where it opens a listener to
process.env.PORT. Because it never opens the listener, Glitch tries to start it over and over again, running the full command in your
start script and trying to install and build your client.
I’d suggest trying to get things running in the console without doing all the initialization stuff in the
start script as a place to begin. Right now I’m seeing the same error I was when I ran
npm run dev in a remix; something about
Cannot find module './keys_dev'. If you stop your project from continually restarting you can more easily troubleshoot your error in the console but working through them one at a time and assembling a working set of
start commands as you fix things. Then you can put that command in your package.json and go from there.
Another thing I’d suggest: on Node project Glitch runs the
start scripts in that order. You could move your initialization commands to the
install script instead of
start and your won’t keep retriggering the
pnpm install every time your project starts.
Lastly, you could put a watch.json file in place to throttle how often install and start run and what file changes trigger those, which might help quiet the noise down.
Hopefully that will get you at least a little further and you can come back to us with more targetted questions about specific problems. Or perhaps someone else in the community can give some specigic pointers to further places to look.