Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TOKEN_INVALID Error #9355

Closed
LimanGit opened this issue Apr 9, 2023 · 1 comment
Closed

TOKEN_INVALID Error #9355

LimanGit opened this issue Apr 9, 2023 · 1 comment
Labels

Comments

@LimanGit
Copy link

LimanGit commented Apr 9, 2023

Which package is this bug report for?

ws

Issue description

E42A4334-1588-4FFB-A31E-F01F7B6861B6

Code sample

const express = require('express');

const app = express();

app.get('/', (req, res) => {
  res.send('Hello Express app!')
});

app.listen(3000, () => {
  console.log('server started');
});

const { Client, RichPresence, DiscordRPCServer } = require('discord.js-selfbot-v13');

const client = new Client();

client.on('ready', () => {
  console.log('Client logged in')
})
client.login(process.env.token)

Package version

1.13.2 v13

Node.js version

18.12.1

Operating system

Linux

Priority this issue should have

High (immediate attention needed)

Which partials do you have configured?

No Partials

Which gateway intents are you subscribing to?

No Intents

I have tested this issue on a development release

No response

@vladfrangu
Copy link
Member

We do not provide support for third party forks, especially those that break Discords terms of service.

@vladfrangu vladfrangu closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants