2 years ago
My deploys started failing, unsure if it's due to my code somehow or if it's something acting up over at Railway. If you have any insights to this I'd be really happy.
==Deploy logs==
Starting Container
container event container died
node:internal/assert:14
throw new ERR_INTERNAL_ASSERTION(message);
^
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at assert (node:internal/assert:14:11)
at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:329:5)
at new ModuleJobSync (node:internal/modules/esm/module_job:313:34)
at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:314:11)
at loadESMFromCJS (node:internal/modules/cjs/loader:1381:24)
at Module._compile (node:internal/modules/cjs/loader:1503:5)
at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
at Module.load (node:internal/modules/cjs/loader:1317:32)
at Module._load (node:internal/modules/cjs/loader:1127:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14) {code: 'ERR_INTERNAL_ASSERTION'
}
Node.js v22.7.0
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
2 years ago
It was definitely an Npm library upgrade issue that caused it, I reverted some of the libs and it deployed as it should.
I'll see if I can isolate the library causing it.
Status changed to Awaiting User Response Railway • over 1 year ago
9 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago