fix: all shards spawning on shard 0 with sharding manager

[almeidx]

process.env.SHARDS only has the shard id (not an array). This meant that we were passing shardIds: 0 to WebSocketManager, which fails this the following if statement, making /ws fetch get all shards and start them on the current process.

discord.js/packages/ws/src/ws/WebSocketManager.ts

Lines 346 to 347 in 4d19426

	public async getShardIds(force = false): Promise<number[]> {
	if (this.shardIds && !force) {

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
discord-js	⬜️ Ignored (Inspect)	Visit Preview		Mar 22, 2025 5:47pm
discord-js-guide	⬜️ Ignored (Inspect)	Visit Preview		Mar 22, 2025 5:47pm

[vladfrangu]

Doesn't this get set to 0,1,2 when having multiple shards per process?

[Qjuh]

Current ShardingManager has no notion of multiple shards per process. But I agree that it should be possible to pass both array of ids and plain number to it, same way it was possible in v14. So instead of this fix it should be added as conversion to array if typeof is number

[Qjuh]

This is not an issue in v14, as it‘s correctly converted to an array there. So nothing to backport.