@discordjs/ws@1.0.0

Bug Fixes

• WebSocketShard: Close errors not being catchable (#9704) (8c782bf)
• WebSocketManager: Always cache result of fetchGatewayInformation (#9611) (df8b6e9)
• WebSocketShard: Handle initial connect being a resume (#9549) (4dcc9c5)

Features

• No-de-no-de, now with extra buns (#9683) (386f206)
  • BREAKING CHANGE: The REST and RequestManager classes now extend AsyncEventEmitter
    from @vladfrangu/async_event_emitter, which aids in cross-compatibility
    between Node, Deno, Bun, CF Workers, Vercel Functions, etc.
  • BREAKING CHANGE: DefaultUserAgentAppendix has been adapted to support multiple
    different platforms (previously mentioned Deno, Bun, CF Workers, etc)
  • BREAKING CHANGE: the entry point for @discordjs/rest will now differ
    in non-node-like environments (CF Workers, etc.)

Refactor

• WebSocketShard: Throttling error handling (#9701) (ceab07b)
• rest: Switch api to fetch-like and provide strategies (#9416) (cdaa0a3)
  • BREAKING CHANGE: NodeJS v18+ is required when using node due to the use of global fetch
  • BREAKING CHANGE: The raw method of REST now returns a web compatible Respone object.
  • BREAKING CHANGE: The parseResponse utility method has been updated to operate on a web compatible Response object.
  • BREAKING CHANGE: Many underlying internals have changed, some of which were exported.
  • BREAKING CHANGE: DefaultRestOptions used to contain a default agent, which is now set to null instead.