Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

cloudstorm

Package Overview
Dependencies
Maintainers
0
Versions
49
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cloudstorm

Minimalistic Discord Gateway library

  • 0.10.11
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
222
decreased by-21.28%
Maintainers
0
Weekly downloads
 
Created
Source

A minimal discord gateway library

Part of the WeatherStack

CloudStorm is a small library specially made to only cover the Gateway area of the discord api.

It makes no assumptions about the rest of your stack, therefore you can use it anywhere as long as you use node 14 or higher.

Some of the things that make CloudStorm awesome:

  • Standalone discord gateway connection
  • zlib-stream, etf and json support
  • Well documented

Example:

const { Client } = require("cloudstorm");
const bot = new Client(token, { intents: ["GUILDS"] });
const startup = async () => {
	await bot.connect();
	bot.on("ready", () => console.log("Bot received ready event"););
};
startup().catch(e => {
	console.error("Error on startup!");
	console.error(e);
});

Gotchas with CloudStorm:

You may wonder how you you are able to get the id of a shard where an event originated from, but don't fear, CloudStorm helps you with that by adding a shard_id property to the events that are forwarded.

So an event you receive may look like this:

{
	"op": 0,
	"t": "PRESENCE_UPDATE",
	"s": 1337,
	"shard_id": 0,
	"d": {
		"user": {
			"id": "id"
		},
		"guild_id": "id",
		"status": "offline",
		"activities": [],
		"client_status": {}
	}
}

Sharding for VERY large bots

CloudStorm supports max_concurrency and gets this info on initial connect, but does not automatically attempt to fetch new info related to max_concurrency. You are expected to re-fetch this data at your own discretion as Discord does not recommend caching the data for extended periods as it can change as your client leaves and joins guilds and possibly cause rate limit errors.

You should start your clusters 1 by 1 as rate limit info is only fetched on Client.connect or when you manually call Client.fetchConnectInfo when /gateway/bot is fetched

Microservice Bots:

I've written a general whitepaper on the idea of microservice bots, which you can find on gist: Microservice Bot Whitepaper

Documentation:

You can find the docs at https://daswolke.github.io/CloudStorm/

Installation:

To install CloudStorm, make sure that you have node 14 or higher on your computer.

Then run the following command in a terminal npm install cloudstorm

FAQs

Package last updated on 27 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc