Where are my deployment geniuses at?

[realfunnyeric]

After switching to Agent v2, I have one app that is quite mature that now I can’t get to deploy.

2025-04-03 10:02:11.75
74ca1d85
User
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
2025-04-03 10:02:11.75
74ca1d85
User
at ModuleWrap. (node:internal/modules/esm/module_job:96:40)
2025-04-03 10:02:11.75
74ca1d85
User
at link (node:internal/modules/esm/module_job:95:36) {
2025-04-03 10:02:11.75
74ca1d85
User
code: 'ERR_MODULE_NOT_FOUND'
2025-04-03 10:02:11.75
74ca1d85
User
}
2025-04-03 10:02:11.76
74ca1d85
System
command finished with error [sh -c node dist/start.js]: exit status 1
2025-04-03 10:02:15.16
74ca1d85
User
Failed to start application: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@db/schema' imported from /home/runner/workspace/dist/index.js
2025-04-03 10:02:15.16
74ca1d85
User
at packageResolve (node:internal/modules/esm/resolve:854:9)
2025-04-03 10:02:15.16
74ca1d85
User
at moduleResolve (node:internal/modules/esm/resolve:927:18)
2025-04-03 10:02:15.16
74ca1d85
User
at defaultResolve (node:internal/modules/esm/resolve:1169:11)
2025-04-03 10:02:15.16
74ca1d85
User
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
2025-04-03 10:02:15.16
74ca1d85
User
at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
2025-04-03 10:02:15.16
74ca1d85
User
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
2025-04-03 10:02:15.16
74ca1d85
User
at ModuleWrap. (node:internal/modules/esm/module_job:96:40)
2025-04-03 10:02:15.16
74ca1d85
User
at link (node:internal/modules/esm/module_job:95:36) {
2025-04-03 10:02:15.16
74ca1d85
User
code: 'ERR_MODULE_NOT_FOUND'
2025-04-03 10:02:15.16
74ca1d85
User
}
2025-04-03 10:02:15.17
74ca1d85
System
command finished with error [sh -c node dist/start.js]: exit status 1
2025-04-03 10:02:15.92
74ca1d85
User
Failed to start application: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@db/schema' imported from /home/runner/workspace/dist/index.js
2025-04-03 10:02:15.92
74ca1d85
User
at packageResolve (node:internal/modules/esm/resolve:854:9)
2025-04-03 10:02:15.92
74ca1d85
User
at moduleResolve (node:internal/modules/esm/resolve:927:18)
2025-04-03 10:02:15.92
74ca1d85
User
at defaultResolve (node:internal/modules/esm/resolve:1169:11)
2025-04-03 10:02:15.92
74ca1d85
User
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
2025-04-03 10:02:15.92
74ca1d85
User
at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
2025-04-03 10:02:15.92
74ca1d85
User
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
2025-04-03 10:02:15.92
74ca1d85
User
at ModuleWrap. (node:internal/modules/esm/module_job:96:40)
2025-04-03 10:02:15.92
74ca1d85
User
at link (node:internal/modules/esm/module_job:95:36) {
2025-04-03 10:02:15.92
74ca1d85
User
code: 'ERR_MODULE_NOT_FOUND'
2025-04-03 10:02:15.92
74ca1d85
User
}
2025-04-03 10:02:15.93
74ca1d85
System
command finished with error [sh -c node dist/start.js]: exit status 1
2025-04-03 10:02:17.18
74ca1d85
User
Failed to start application: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@db/schema' imported from /home/runner/workspace/dist/index.js
2025-04-03 10:02:17.18
74ca1d85
User
at packageResolve (node:internal/modules/esm/resolve:854:9)
2025-04-03 10:02:17.18
74ca1d85
User
at moduleResolve (node:internal/modules/esm/resolve:927:18)
2025-04-03 10:02:17.18
74ca1d85
User
at defaultResolve (node:internal/modules/esm/resolve:1169:11)
2025-04-03 10:02:17.18
74ca1d85
User
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
2025-04-03 10:02:17.18
74ca1d85
User
at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
2025-04-03 10:02:17.18
74ca1d85
User
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
2025-04-03 10:02:17.18
74ca1d85
User
at ModuleWrap. (node:internal/modules/esm/module_job:96:40)
2025-04-03 10:02:17.18
74ca1d85
User
at link (node:internal/modules/esm/module_job:95:36) {
2025-04-03 10:02:17.18
74ca1d85
User
code: 'ERR_MODULE_NOT_FOUND'
2025-04-03 10:02:17.18
74ca1d85
User
}
2025-04-03 10:02:17.19
74ca1d85
System
command finished with error [sh -c node dist/start.js]: exit status 1
2025-04-03 10:02:18.43
74ca1d85
System
crash loop detected

I did everything “Sam” told me to do, but to no avail. Need help on this one.

[realfunnyeric]

Keeps getting better

[realfunnyeric]

I’m sending out an SOS!

[realfunnyeric]

Agent literally can’t stop, won’t stop. It’s unhinged, refusing to listen - just editing code despite kill 1 command - it just reboots and keeps going. ITS MADNESS

[realfunnyeric]

Guys, we are so screwed. Once these robots reach a certain point, humans are toast lol

[mark]

Are you able to click the stop button above the chat with Agent? Or maybe try Ctrl + Enter on desktop? (Replit Docs)

Also, not sure, but can you temporarily change anything in the Workflows? Then try to stop again? (Replit Docs)

[realfunnyeric]

fart noises

[archness]

I did encounter this issue yesterday where it all locked up and I had to kill the whole thing, close my browser, and re-open it to get the workspace responding again.

[mrpreben]

Have you tried explaining the issue to ChatGPT and asked for a prompt you can provide it that might work? That’s what I do when I get stuck, and it tends to work. ChatGPT will assess potential causes for the issuse, and give you a prompt. More often than not, this method works for me Then you can both explain what the issue might be, give it potential fixes, and help it out of the loop. Starting a new agent chat is also something I’ve had to do when getting the error.

[realfunnyeric]

Yeah I do that all the time. And I also use Grok when Chat can’t figure it out.

I was able to overcome this. I can’t tell you how. I just know that I banged on the keyboard for a few hours and it came back to life.

[hypler]

Ahh the old, turned it off and turn it on again. Hopefully you got this working, I had a similar issue on my first build of my app. This was in December so i ended up starting over since the agent sucked then lol.

[EthanTorbenson]

Just an FYI, LLMs at the end of the day are algorithms. When you put input in, they’re bound to give output out, so when you say stop, you’re forcing it to answer. I would suggest starting a new chat, or pausing the agent, and refreshing the environment. It’s not super productive to say stop…