The application did not respond + err

[aWhiteHatCoder]

Describe the bug

I was following the discord.js code EXACTLY I ran the code but got the resulting error:

`node:events:491
throw er; // Unhandled 'error' event
^

TypeError: Cannot read properties of undefined (reading 'get')`

After throwing in (at the index.js file):

client.on('error', (err) => { console.log(err.message) });

I got a new error saying client is not defined. Each time I run the /ping command I get the "The application did not respond" error as a reply.

To Reproduce

(.-.)/ follow the code exactly

(lol I spent a couple hours debugging and it still fails. I guess I am just a crappy coder.)

Screenshots

Device (please complete the following information)

Device : Windows 10 computer w/ vs code
Browser : Chrome Version 106.0.5249.119 (Official Build) (64-bit)

Additional notes

Have a great rest of your day! I wish thy no pesky insects.

[almostSouji]

TypeError: Cannot read properties of undefined (reading 'get')`

Whatever is in front of that .get is undefined - you can read in the error stack trace which section of code it is exactly

I got a new error saying client is not defined.

Then you didn't define the identifier client - which the guide does
(the section you linked is a rest deploy and doesn't even have a client in it's scope, so I have no idea where that error may originate from, again, read the stack trace)

"The application did not respond"

Simply means that you don't send a response. If you are following the guide, that'd be placed in the respective execute() call, as demonstrated here.

When you are done with a section, you can review the resulting code and compare it with yours to make sure you didn't miss anything.

[almostSouji]

If this is indeed a bug with the guide, please provide the exact part of the guide you are receiving the error from.

[aWhiteHatCoder]

Hello! Thank you so much for viewing my issue.

This is the line of code that had an error (this is in interactionCreate.js in the events folder

https://github.com/discordjs/guide/tree/main/code-samples/creating-your-bot/event-handling

I am at this point in the section and I tried using the exact code. (i also added and ran deploy-commands + the commands folder with ping.js)

This is the current error I am faced with:

Perhaps I did something wrong with the file paths? Is there something I need to install?

(Sorry I do code in VS super light mode)

[monbrey]

This suggests that you haven't defined client.commands, which is covered in the Loading command files section on one of the earlier pages

[aWhiteHatCoder]

const command = client.commands.get(interaction.commandName);

This is the line I am currently getting an error from as client.commands.get is not doing anything. What does client.commands.get even do? (sorry for asking a most likely very obvious question)

[monbrey]

Yes, I know that's where you're getting the error from.

It gets your command file from a previously loaded collection of commands. You appear to have skipped that step, which I provided as a link.

[tingalicious]

The fact that the client commands still needs to be kept at the index.js scope is slightly confusing for newer developers when looking at the sample code on github; since the sample for the event handling tutorial does not include the client.commands collection instantiation or population, there is an implication that the logic to loop through all the command files and populate the client commands collection is to be moved elsewhere like the rest of the command handling logic that was moved into interactionCreate.js, even though they are not referenced in interactionCreate.js. The tip indicating that the client object from index.js was passed to interactionCreate.js scope by the interaction should be helpful for understanding this relationship, but I think omitting that logic from the sample code and the tutorial generates some confusion on this front.

[monbrey]

We can look at reviewing this, but tutorial code and samples is meant to teach concepts. If it's being blindly copy pasted, I don't believe that's our fault.