Aura

There are merge conflicts, please rebase.

You wait for the one in /rest

There are merge conflicts that need resolving, but otherwise LGTM.

I'm confused, what's the issue with [`@discordjs/rest`](https://www.npmjs.com/package/@discordjs/rest), which can be used standalone without the main library?

> > **Should we support have a raw data approach, or a command approach?** > > > > * **If the latter, should we have `eval`?** > > I think...

> * **What should be done when a message is sent from shard A to shard B, but B hasn't signalled "ready" (and is not "exit")? Should it wait for...

You can do one of the following solutions if you have the fork downloaded locally: 1. Use `yarn link` inside the `packages/discord.js` directory and in your application's folder. 1. Run...

@imranbarbhuiya are you still able to reproduce this? Does the sample above work for you?

The issue you're mentioning isn't related at all to actions or gateway handlers, just about an specific structure doing something outside of them. To answer you, the cache retrieval is...

We already support `max_concurrency` in `@discordjs/ws`, see [here](https://github.com/discordjs/discord.js/blob/3c231ae81a52b66940ba495f35fd59a76c65e306/packages/ws/src/utils/IdentifyThrottler.ts#L22). `@discordjs/sharder` won't handle those, that's `@discordjs/ws`'s job. The sharder will have an independent system based on strategies, how it'll play out in...