Stuck on an issue?

What’s happening? The bot used to start up, however it doesn’t anymore. All the tokens are still valid

Logs

> muse@2.1.0 start
npm run env:set-database-url -- esmo src/scripts/migrate-and-start.ts

> muse@2.1.0 env:set-database-url
> esmo src/scripts/run-with-database-url.ts
(node:446435) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/errors:477
     ErrorCaptureStackTrace(err);
     ^
Error [ERR_LOADER_CHAIN_INCOMPLETE]: "file:///root/runner/private/lh-music/node_modules/esbuild-node-loader/loader.mjs 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include `shortCircuit: true` in the hook's return.
    at new NodeError (node:internal/errors:387:5)
    at ESMLoader.resolve (node:internal/modules/esm/loader:860:13 
    at async ESMLoader.getModuleJob (node:internal/modules/esm/loader:439:7)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:541:24)
    at async loadESM (node:internal/process/esm_loader:83:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12) {
    code: 'ERR_LOADER_CHAIN_INCOMPLETE'
}

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

Runtime I’m running Muse:

• Directly from the cloned repository
• Inside a Docker container
• Something else (please elaborate)

Versions

• Muse: 2.1.0 (the same issue occurs on 2.1.1 as well)
• Docker (if applicable):
• OS: Arch Linux
• ffmpeg: (if running outside the Docker container, 4.1 or later is required) 5.0.1