Merge pull request #165 from cainthebest/fix/add-guard-for-dev-mode

Fix: add guard for dev mode

Author: ghostdevv

.changeset/rich-bugs-tickle.md

@@ -0,0 +1,5 @@
+---
+'jellycommands': patch
+---
+
+add a guard to catch no guild id when dev mode enabled

docs/guide/commands/dev.md

@@ -18,6 +18,10 @@ const client = new JellyCommands({
 
 For additional options, see [dev options](/api/client#dev).
 
+:::tip NOTE
+If `dev` mode is enabled, at least one guild id must be specified within [`dev.guilds`](/api/client#dev)
+:::
+
 ## Global Dev Mode
 
 Adding `dev: true` to every command *(and remembering to remove it)* can be tedious. [global dev mode](/api/client#dev-global) makes this easier.

packages/jellycommands/src/JellyCommands.ts

@@ -51,6 +51,17 @@ export class JellyCommands extends Client {
         if (this.joptions.commands) {
             const commands = await resolveCommands(this, this.joptions.commands);
             const commandIdMap = await getCommandIdMap(this, commands);
+            if (!this.joptions.dev?.guilds?.length) {
+                const hasDevCommand = Array.from(commands.commands).some(
+                    (command) => command.options.dev,
+                );
+
+                // If dev is enabled in some way, make sure they have at least one guild id
+                if (this.joptions.dev?.global || hasDevCommand)
+                    throw new Error(
+                        'You must provide at least one guild id in the dev guilds array to use dev commands',
+                    );
+            }
 
             // Whenever there is a interactionCreate event respond to it
             this.on('interactionCreate', (interaction) => {