You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guide/additional-info/updating-from-v14.md
+24
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,10 @@ Make sure you're using the latest LTS version of Node. To check your Node versio
14
14
15
15
`ApplicationCommand#dmPermission` and `ApplicationCommand#setDMPermission()` have been removed. This was legacy functionality for commands—use contexts instead.
16
16
17
+
### ApplicationCommandManager
18
+
19
+
`ApplicationCommandManager#fetch()` method has been updated for consistency with other managers. Previously, it accepted two parameters: `id` (a snowflake or an options object) and an `options` object. Now, it only accepts a single `options` argument, which can be a snowflake or an options object that may include an `id` property.
20
+
17
21
### AnnouncementChannel
18
22
19
23
`AnnouncementChannel#addFollower()` now returns `FollowedChannelData` instead of a snowflake. This helps to expose the created webhook id in the target channel.
@@ -24,6 +28,10 @@ Make sure you're using the latest LTS version of Node. To check your Node versio
24
28
25
29
### Client
26
30
31
+
#### Emojis
32
+
33
+
`Client#emojis` has been removed due to confusion with the introduction of application emojis and performance impact. Use the `resolveGuildEmoji()` utility function to get a cached guild emoji.
34
+
27
35
#### Ping
28
36
29
37
`Client#ping` has been added to replace the old `WebSocketManager#ping`. This will be `null` when the heartbeat from the gateway is yet to be received.
@@ -67,6 +75,10 @@ The underlying WebSocket behaviour has changed. In version 14, this was a non-br
`ClientEvents` type has been removed. Use `ClientEventTypes` instead. This change ensures consistency with the rest of the event types across the library.
81
+
70
82
### ClientOptions
71
83
72
84
Removed `ClientOptions#shards` and `ClientOptions#shardCount` in favor of `ClientOptions#ws#shardIds` and `ClientOptions#ws#shardCount`.
@@ -135,6 +147,10 @@ emoji.imageURL();
135
147
136
148
`Emoji#url` has been removed. To allow more granular control of the returned extension, Use `Emoji#imageURL()` instead.
137
149
150
+
### EventEmitter
151
+
152
+
`BaseClient`, `Shard`, `ShardingManager`, and `Collector` now extend `AsyncEventEmitter` instead of `EventEmitter`. This comes from [@vladfrangu/async_event_emitter](https://npmjs.com/package/@vladfrangu/async_event_emitter).
153
+
138
154
### Events
139
155
140
156
-`Events.ShardError` has been removed.
@@ -160,6 +176,10 @@ This utility has been removed. Everything in this class is redundant as all meth
160
176
161
177
Removed `Guild#shard` as WebSocket shards are now handled by @discordjs/ws.
162
178
179
+
### GuildApplicationCommandManager
180
+
181
+
`GuildApplicationCommandManager#fetch()` method has been updated for consistency with other managers. Previously, it accepted two parameters: `id` (a snowflake or an options object) and an `options` object. Now, it only accepts a single `options` argument, which can be a snowflake or an options object that may include an `id` property.
182
+
163
183
### GuildAuditLogs
164
184
165
185
`GuildAuditLogsEntry.Targets.All` has been removed. It was not being used.
@@ -172,6 +192,10 @@ Removed `Guild#shard` as WebSocket shards are now handled by @discordjs/ws.
172
192
173
193
`GuildChannelManager#addFollower()` now returns `FollowedChannelData` instead of a snowflake. This helps to expose the created webhook id in the target channel.
174
194
195
+
### GuildMemberResolvable
196
+
197
+
`GuildMemberResolvable` type has been removed. It was defined as `GuildMember | UserResolvable`, but `UserResolvable` already includes `GuildMember`. Use `UserResolvable` instead.
198
+
175
199
### MessageManager
176
200
177
201
`MessageManager#crosspost()` has been moved to `GuildMessageManager`. This means it will no longer be exposed in `DMMessageManager`.
0 commit comments