[TS] Nodemon x ShardingManager never emits ready

As stated above, using nodemon with Djs sharding manager never emits ready for any of the shards. The Debug Event does not emit anything dev script: npx nodemon ./src/index.ts package.json https://github.com/AyakoBot/Ayako-v2/blob/main/package.json nodemon.json https://github.com/AyakoBot/Ayako-v2/blob/main/nodemon.json tsconfig.json https://github.com/AyakoBot/Ayako-v2/blob/main/tsconfig.json index.ts https://github.com/AyakoBot/Ayako-v2/blob/main/src/index.ts D.js v14.13.0 Node v20.4.0
2 Replies
d.js toolkit
d.js toolkit8mo ago
- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button!
Lars_und_so
Lars_und_so8mo ago
<a:kelly_nooo:1168852140404523109> i hate having to restart the shard just to apply a small change in dev is there a better way to re-cache modules in ESM? if it was possible, i'd love to be able to wrap the shard code into a nodemon-like module that allows me to refresh changed files im aware i shouldnt, in ESM Nodemon uses a special import method that forces node to re-cache the modules using query parameters for example import x from 'y' !== import x from 'y?date=1' since i shouldnt, and dont want to, restart my shards often, i want to use nodemon to update my import statements as i code. I also understood that using nodemon to start the sharding manager doesnt do anything, so how do i start the shards using nodemon, instead of starting the sharding manager using nodemon does the sharding manager support a dev mode at all? or am i better off not using the sharding manager for development why dont u recommend it? nah it only has 1 shard tho as it turns out i cant even run bot.ts with nodemon, it just doesnt emit ready either so ill drop trying to get it to work