djs-in-dev-version

[dawn phoenix]

Drop your Q's we will find some A's

⚠️ You are using a development build. Things might break at any new commit.
please provide the full version (output of npm ls discord.js | yarn list discord.js | yarn why discord.js (yarn v3+) | pnpm list discord.js) you have installed when asking for support!

Please open threads for questions you anticipate might take some more time or back and forth to resolve

npm remove discord.js
npm install discord.js@dev

yarn remove discord.js
yarn add discord.js@dev

pnpm remove discord.js
pnpm install discord.js@dev

bun remove discord.js
bun add discord.js@dev

• Requires version 22.12 or later of Node.js
• Documentation: https://discord.js.org/docs/packages/discord.js/main

What can you expect from the development version?

Use without crashes
Free of bugs
Consistent API (Things may change drastically from one commit to the next)
Refactor a large code base that a lot of people depend on to use this build

[fast tulip]

why i can type here

@dawn phoenix

dats dope

did u forget to lock the channel or what

[dawn phoenix]

what?

[fast tulip]

is that normal to type here?

[dawn phoenix]

this is a support channel for people trying out v14 by installing the at-dev build

[quiet aurora]

no this is a discussion channel for discord.js@dev

[fast tulip]

oh ahem

[jolly pike]

cool

[fast tulip]

sorry abt that bois

[rigid haven]

ohh ok i was confused too

[dark wharf]

Anyway, back to the channel topic

[torn osprey]

I know that I shouldn't ask it, and I know that I might not receive an answer to this question, but: is there a general ETA? Like before discord makes reading messages privileged intents?
I have been procrastinating updating my bot from v12 to v13, but if this comes before that discord intent update, I might be able to update straight to v14.

And again, sorry for this question. And I understand that there might not even be a date for a push to main (yet)

[swift orchid]

What alternatives are there to .deleted? Is there anything stopping me from unknowingly storing a reference to a now-deleted channel? I suppose we're just expected to .catch() all our function calls, is that correct?

[outer bane]

the alternatives are laid out in https://github.com/discordjs/discord.js/issues/7091

[knotty plover]

I think the intention was to have it out before then, but its probably not a hard requirement. The privileged intent for access to message content would probably be compatible with v13 as a minor change if it was required (e.g. 13.7)

[sturdy kiln]

Is the "Ask to join" button for RPC a v14 feature? Because I can't find any way to integrate it right now.

[torn osprey]

Oh yea, I don't think it would be a major update, but it would be nice if I could update my bot to v14 in one go, instead of going for v13 first and then (after some more procrastinating) to v14 😶

[knotty plover]

RPC is not a discord.js feature at all

[sturdy kiln]

Oh ok, I thought it was following the same updates

[knotty plover]

Im not sure what button you're referring to anyway

[sturdy kiln]

When you play a game, there's a button called "Ask to join" that user B can press and ask player A to join in that game lobby

I've asked for support in #archive-rpc-help, but's like 2 days and no answer

[plain rover]

Activity#buttons
The labels of the buttons of this rich presence

[knotty plover]

You can read the buttons on a presence with discord.js

But otherwise, bots cannot create/set/interact with them

[sturdy kiln]

It's not a presence button, is a default button that discord create when you put the secrets in the presence, so other user can join the game

[knotty plover]

Are you sure? Because the game is definitely an Activity

[sturdy kiln]

Yeah, pretty sure

[knotty plover]

And its not a "presence" in the way bots use them, its RPC and its coming from the game on your local machine

[sturdy kiln]

I've also checked the docs here https://discord.com/developers/docs/topics/rpc, there's an event called ACTIVITY_JOIN_REQUEST

But if I subscribe the client to that event, it never get fired, both on user A client nor user B

[knotty plover]

That is RPC

Bots cant join activities

You're looking at entirely user-land features here

These are not features of discord.js, because a bot
A) cannot set activities that can be joined
B) cannot join activities

[sturdy kiln]

Yeah I know, I'm talking about RPC, I was writing here asking if somebody knows if that is already a feature or it's planned to be added

[knotty plover]

Then this is the wrong channel, because this is for discussion of the discord.js dev release

RPC is not part discord.js

[sturdy kiln]

Sorry, I thought the new version 14 brought updates for the rpc as well

[tame gazelle]

all changes aren’t in the guide 'cuz v14 is still in dev right?

[long narwhal]

I mean, all current changes are in the guide.
https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#before-you-start has what I'd presume is all current ones

[umbral slate]

Should we make threads for ongoing issues to draw more attention to them?

I've already opened an issue on GitHub but it got no attention and it's pretty important

[velvet jasper]

Which ones are these?

[umbral slate]

only referring to https://github.com/discordjs/discord.js/issues/7342 atm

[brave mulch]

Noice

[knotty plover]

Wouldn't work imo, nobody looks at threads

#archive-library-discussion is the place to discuss development, issues etc

[umbral slate]

aight I figured, just asking cuz of Souji's message above. There isn't much to discuss, the bug is reported and it's pretty straightforward, just need someone who knows how to fix it because I've tried it and I can't figure it out

[knotty plover]

Yeah idk, I did the initial component design but theres been so much change, especially with typings, since then that I dont want to touch it lol

[umbral slate]

The only issue with that bug is the fact that some types are made out of unions, so Omit doesn’t work on them

[proper cape]

So

Embed.addFields([/* Some api fields */]);

is throwing

ZodError: [
  {
    "code": "invalid_type",
    "expected": "object",
    "received": "array",
    "path": [
      0
    ],
    "message": "Expected object, received array"
  }
]

which i assume is a bug?

[velvet jasper]

can you show what you're putting in your array?

[proper cape]

Heres the actual embed

new Embed()
    .setColor(grass)
    .setTitle('Welcome to #help')
    .addFields([
      { name:'Please keep conversations related to questions and answers.', value: 'Take other off topic conversations to their appropriate channels.' },
      { name:'You will be pinged when someone asks for help in #HelpDesk', value:'To avoid the ping, remove the help role using the button there.' },
    ])

i assume the parser doesnt hate trailing commas but idk

[velvet jasper]

Oh I see, don't put it into an array, it's a variadic parameter so just put commas between them

like this:

.addFields(
      {
        name: 'Please keep conversations related to questions and answers.',
        value:
          'Take other off topic conversations to their appropriate channels.',
      },
      {
        name: 'You will be pinged when someone asks for help in #HelpDesk',
        value:
          'To avoid the ping, remove the help role using the button there.',
      }
    );

[proper cape]

oh... would be nice if the docs reflected that

current docs are relatively misleading in that case

[uncut kelp]

It's probably spread and doesn't show that

[proper cape]

probably, the link to src not working currently makes checking that annoying as well

[uncut kelp]

What page is this?

[proper cape]

Builders module, main branch, Embed

i assume main is on @digital dust @ dev

woops sorry about that ping

[uncut kelp]

Yeah it accepts a spread and seems the documentation don't wanna put that in

[proper cape]

in the function its spread, is it spread in the jsdoc?

because the documentation reads from jsdoc

[uncut kelp]

Ah uh this is TypeScript, we use typedoc

[deep jetty]

its typescript theres no types in the jsdoc

[proper cape]

oh wait right

welp i guess its just a matter of whenever the documentation website gets updated

[distant prawn]

Should I update my bot to v14 now? Or wait until the stable version is released.

[vocal sapphire]

You can update, just expect some breaking changes sometimes

[lethal trail]

What is changed is v14?

[feral cobalt]

https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#before-you-start

[scarlet tangle]

Hey checking out the guide and I saw this

In addition, #isCommand, now indicates whether the command is an application command or not. This differs from the previous implementation where #isCommand indicated if the interaction was a chat input command or not.

• https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#interaction
  but I don't really get what it means? Is application commands more broad then chat input commands? Is it only triggering for actual application commands and not guild ones for some reason?

[velvet jasper]

Is application commands more broad then chat input commands

yes

you can have chat input commands, user commands, or message commands

[scarlet tangle]

So isCommand now triggers for all 3 cases?

[velvet jasper]

it's true for all 3 of those cases yeah

[scarlet tangle]

wait what's a chat input command vs message command

[velvet jasper]

user and message commands are the context menu commands

chat input commands are slash commands

[scarlet tangle]

ahhh, ok

Out of curiosity do you know any use cases where someone would use the more broad one over the specific ones?

[twilit bobcat]

they're all technically commands

context menu interactions extend the base command interaction class

[scarlet tangle]

oh i guess in djs they are

One such use case could be to handle the application commands (chat input + context menus) together in one handler

[velvet jasper]

yes my command handler handles any kind of command, so having a typeguard that checks if it is any command type is useful

[twilit bobcat]

it's that way on the discord api, it's not really a djs thing

they're registered the same way you register any application command

just with a USER / MESSAGE type instead of CHAT_INPUT and other stuff like lack of options

[scarlet tangle]

Oh yeah, don't know how i forgot about that

[icy dew]

So i use numbers for types in slash commands, are they subject to change?

(e.g. i use type: 1 for chat input, and for options i use type: 3 for STRING)

Is it better to use exported values or are they the same?

[knotty plover]

Numbers are fine

[icy dew]

alright, thanks

[umbral slate]

For readability of your code it’s better to use the enums, otherwise no since enums hold numbers

[icy dew]

i prefer numbers, probably since I've used them a lot now

[woven grove]

your question is "are they subject to change"

every value is

hence the enums

[icy dew]

ah alright then

[summer elbow]

Is there a What’s new page of sorts for the dev branch?

Or is it just the refactoring for the name changes and enums?

[scarlet tangle]

in progress (obviously): https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#before-you-start

[deep jetty]

theres the commit history if you want a full list but theres a WIP migration guide page ^

[summer elbow]

Oo thanks, didn't think of checking commit history

[split fulcrum]

What is new in v14?

Or what will be new?

[vague coyote]

[split fulcrum]

Okm

[obtuse crater]

Is it intentional that <User>.flags.toArray() always returns None, even when user has flags?

[vague coyote]

well, did you fetch the flags

[obtuse crater]

Yes

[velvet jasper]

Sounds like unintentional behavior, if you could, can you submit an issue ticket?

[obtuse crater]

Sure

[lost ledge]

Will modals be implemented in v13 or v14?

[velvet jasper]

most likely v14

[lost ledge]

oh alright

[cinder scaffold]

Why djs v14?

[vague coyote]

Why not?

[cinder scaffold]

I think no need of it

V13 was enough

[woven grove]

lol

[vague coyote]

lmao

[velvet jasper]

[silk topaz]

damn

[scarlet tangle]

hey discord..js v14 not support @dry tulipjs/builder

[vague coyote]

what

thats a separate package siris is more intelligent than me

[velvet jasper]

Builders are re-exported from djs now

[scarlet tangle]

_- no becuase

+ const { ApplicationCommandType, ApplicationCommandOptionType } = require('discord.js');

const command = {
  name: 'ping',
- type: 'CHAT_INPUT',
+ type: ApplicationCommandType.ChatInput,
  options: [
    name: 'option',
    description: 'A sample option',
-   type: 'STRING',
+   type: ApplicationCommandOptionType.String
  ],
};```

we need to change if (!interaction.isCommand()) return;?

[vague coyote]

<Interaction>.isCommand() checks if the interaction is a CommandInteraction

so, thats up to you

[scarlet tangle]

what interaction.isChatInputCommand()

[vague coyote]

CHAT_INPUT -> CommandInteraction -> isCommand()

[scarlet tangle]

so we need change it?

[vague coyote]

I have no idea what you want xD

<Interaction>.isCommand() checks if the interaction is a CommandInteraction
so, thats up to you

[slim wharf]

Imma go with the raw types, djs does so many changes, so you can't stay on one.

[woven grove]

the enums are "raw"

because they are -types enums

[velvet jasper]

You should avoid magic numbers, people are less likely to know what “1” means compared to ApplicationCommandType.ChatInput

Also let’s assume discord changes the type of chat input to “2”, if you’re using an enum you wouldn’t be affected by this change

[icy dew]

just curious, has that ever happen (ik it's subject to change, but has it changed in the past)

[scarlet tangle]

doesn't that checks if the interaction is an application command one?

[icy dew]

yea i was thinking the same thing coz

[timid talon]

How to install discordjs dev version using yarn

[scarlet tangle]

yarn add discord.js@dev Read the pins

or the channel topic, whichever feels closer

[timid talon]

only npm in pins

[scarlet tangle]

You don't need anything special for yarn

[timid talon]

oh ok

[scarlet tangle]

just add the @dev tag

[vague coyote]

I should stop looking at stable docs when giving support in here

[median jetty]

guild get response undefined

[urban belfry]

@median jetty client hasn't logged in yet, the cache hasn't filled up, that's expected

[median jetty]

Always responds undefined

[vague coyote]

yes, thats intended behaviour.

Not sure what you expect.

The client isn't ready, thus has no data.

[hollow spoke]

v14 preperation? 😳

[vague coyote]

yes?

minor versions wont do it in long term

[timid talon]

Why isn't Embed#setColor("BLURPLE") not working

[uncut kelp]

It doesn't parse strings iirc

[timid talon]

oh

[uncut kelp]

For now you can import resolveColor() from Util and do <Embed>.setColour(<Util>.resolveColor("BLURPLE")) or something

[timid talon]

It gives me this error

ZodError: [
{
"code": "invalid_type",
"expected": "number",
"received": "string",
"path": [],
"message": "Expected number, received string"
}
]

[timid talon]

oh ok

[uncut kelp]

Yea it's currently a known issue. I think something is gonna be done to remedy it, but not sure just yet

[timid talon]

Thanks

[median jetty]

I can made video on youtube on djs v14

[uncut kelp]

You what

[median jetty]

I can make a video on v14

[uncut kelp]

Okay

o,o

[tall verge]

Hello, does anyone know where the list of permissions?

[uncut kelp]

What is a permit

[tall verge]

anyone?

[uncut kelp]

You want #djs-help-v14

Go there and ask

[tall verge]

I mean all permissions names of v14

._.

[uncut kelp]

I mean nothing has changed

Do you mean this from discord-api-types?
https://github.com/discordjs/discord-api-types/blob/main/payloads/v9/permissions.ts#L14

[tall verge]

yes, thank you

[uncut kelp]

You're welcome!

[tardy frost]

i think the second thing is supposed to be "YARN" instead of "NPM"

[dawn phoenix]

you'd think correctly

[undone yew]

        "GUILD_MEMBERS",
        "GUILD_BANS",
        "GUILD_EMOJIS_AND_STICKERS",
        "GUILD_INTEGRATIONS",
        "GUILD_WEBHOOKS",
        "GUILD_INVITES",
        "GUILD_VOICE_STATES",
        "GUILD_PRESENCES",
        "GUILD_MESSAGES",
        "GUILD_MESSAGE_REACTIONS",
        "GUILD_MESSAGE_TYPING",
        "DIRECT_MESSAGES",
        "DIRECT_MESSAGE_REACTIONS",
        "DIRECT_MESSAGE_TYPING"

what is the name of these intents in v14?

[icy dew]

Same, but PascalCase instead of SCREAMING_SNAKE_CASE iirc

[urban belfry]

https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#common-client-initialization-changes

[undone yew]

I ask your name and none of them have a name

[uncut kelp]

The names are here https://github.com/discordjs/discord-api-types/blob/main/gateway/v9.ts#L174

[urban belfry]

the names are the same, just the style's have changed

[uncut kelp]

You import from discord-api-types

[undone yew]

no

[icy dew]

.

GUILD_MEMBERS become GuildMembers

and so on

[median jetty]

When will version 14 of djs

[undone yew]

tthanks

[urban belfry]

there's really no telling.. yet

[tame gazelle]

is it still possible to use them as string (like intents in v13) ?

[undone yew]

@uncut kelp how to import?

[urban belfry]

literally the guide i've sent

[uncut kelp]

You were told above

[icy dew]

docs say yes, you can use an array of IntentsResolveable - which include strings

[median jetty]

Version 14 may be buggy

[urban belfry]

yeah but it would be like so intents: ["Guilds", "GuildMembers"]

[tame gazelle]

same for partials?

[velvet jasper]

No it’s uses the enum so GatewayIntentBits.Guilds and so on

[undone yew]

I loaded the module

how do i import it?

[uncut kelp]

It's literally above

In many screenshots

Many people talking

[undone yew]

I using

[icy dew]

hmm so docs aren't updated?

[velvet jasper]

Which docs?

[icy dew]

because i checked the main branch and the IntentsResolveable accept strings

[uncut kelp]

These, because this includes the string variant

I guess they're not updated

[tame gazelle]

nice thanks

[velvet jasper]

Oh yeah gotta fix that

[icy dew]

https://discord.js.org/#/docs/discord.js/main/typedef/IntentsResolvable

oh you found it

[velvet jasper]

Correction this: #djs-in-dev-version message

[urban belfry]

@tame gazelle

[velvet jasper]

Lol

[tame gazelle]

it works like this

no error

[velvet jasper]

Hmmmm

[urban belfry]

i checked strings, it worked, then i updated, now it doesn't work

[icy dew]

I'm confused now

[tame gazelle]

it's the latest dev right?

[icy dew]

lemme check npm

[vague coyote]

14.0.0-dev.1643544396.388f535

seems about right

[icy dew]

14.0.0-dev.1643544396.388f535

[tame gazelle]

then this works fine ^

[icy dew]

I'm slow

lol

[icy dew]

even partials?

[tame gazelle]

I didn't get error like BITFIELD_INVALID so yes ig

[icy dew]

hmm alright

[vague coyote]

I highly doubt thats working

[velvet jasper]

Are you receiving guild events?

[tame gazelle]

gonna try

interactionCreate only needs Guilds intent right?

so I can test a / command?

[icy dew]

idk

iirc yes

[tame gazelle]

I'll add guildCreate event

[icy dew]

or that

hea

[tame gazelle]

for make sure

[urban belfry]

just add GuildMessages (with Guilds of course) and a messageCreate listener

[icy dew]

you can try using GuildMessages

[tame gazelle]

it works

get an error inside the guildCreate event but it works ._.

[icy dew]

what error?

[tame gazelle]

Discord.MessageEmbed isn't a constructor

[icy dew]

ah

[dawn phoenix]

Embed

[icy dew]

So intentional or bug

for intents using array of strings

[velvet jasper]

Are you trying to make an embed on your end or are you just receiving that error regardless?

[tame gazelle]

regardless

[velvet jasper]

Ok that’s a bug then

[tame gazelle]

I didn't update all the code yet

[velvet jasper]

Do you have more than one listener for guildCreate?

[tame gazelle]

I meant that I have the error in my code

it's not a d.js issue

[velvet jasper]

Ok

[tame gazelle]

I didn't get correctly your question ._.

we cannot pass string for .setColor() ?

[icy dew]

nope

use the resolver

[velvet jasper]

We’ll look into this

[icy dew]

I'm assuming this is the same for JSON embeds as well?

[velvet jasper]

Iirc that would work there

[tame gazelle]

what's that?

[icy dew]

hmm ill try and see s

[slow storm]

Util.resolveColor

[plain rover]

Documentation suggestion for @tame gazelle:
(static) Util.resolveColor()
Resolves a ColorResolvable into a color number.

[icy dew]

ignore mine, use ^

oh it wasn't in the guide, i saw it somewhere else mb

[tame gazelle]

and VSC is saying that <GuildChannel>#isText() is still a method

[icy dew]

it is

[tame gazelle]

ah yeah

[finite fog]

It's doing something slightly different now.

[plain rover]

GuildChannel#isText()
Indicates whether this channel is a [TextChannel](<https://discord.js.org/#/docs/discord.js/main/class/TextChannel>).

[tame gazelle]

only for TextChannel now?

[icy dew]

TextBased includes GuildNews , Text and so on

[vague coyote]

isTextBased() is the old isText() and is isText() is now only a guild text channel

[icy dew]

also I'm assuming this is a discord bug right? (links not resolving) or is it docs

[vague coyote]

works for me

[icy dew]

I'm on mobile

so Discord ig

[woven grove]

*android

[vague coyote]

can confirm, doesn't work on android

[tame gazelle]

so this will not get removed? ._.

[vague coyote]

what will not get removed

[urban belfry]

using strings for intents

[tame gazelle]

and partials

[woven grove]

yeah you cant use strings

use the enums

[icy dew]

alright

[tame gazelle]

in the latest dev I can so it means that you will remove this?

[icy dew]

probably, since it isn't intended

[woven grove]

most likely

[scarlet tangle]

is this right js const client = new Client({intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildVoiceStates, GatewayIntentBits.GuildMessageReactions]});

[urban belfry]

looks fine, try it

[scarlet tangle]

idk how much changes happen

so this changejs const { MessageEmbed } = require("discord.js"); now js const { Embed } = require("discord.js");

[tame gazelle]

yup

[scarlet tangle]

what change happen in button?

[tame gazelle]

check the guide in the pin

[velvet jasper]

https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#messagecomponent

[scarlet tangle]

const but = new MessageButton().setCustomId("ne").setLabel("1").setStyle("SECONDARY");``` is this change?

[velvet jasper]

nope

[scarlet tangle]

so it same ?

[velvet jasper]

no, please check the guide

[scarlet tangle]

it not open in my country

[velvet jasper]

you need enums instead of strings

[scarlet tangle]

Did you mean discordjs.guide?
The site you just tried to visit looks fake. Attackers sometimes mimic sites by making small, hard-to-see changes to the URL.```

[scarlet tangle]

what you mean can you explain me pls

[velvet jasper]

sorry I can't spoonfeed this, if you don't need v14 right now please just stick to v13

[finite fog]

Click "Ignore", whatever that warning is about.

[scarlet tangle]

no asking for example

not say for spoonfeed

you not change my code

just give ma small example

that not call as spoonfeed

[velvet jasper]

https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#messagecomponent

[scarlet tangle]

what is this js const { EnumResolvers } = require('discord.js'); const enumValue = EnumResolvers.resolveButtonStyle('PRIMARY');

[vague coyote]

its explained there...

[scarlet tangle]

cant understand soory

idk where it work for

[vague coyote]

just a question, why do you use the dev version and not v13

[scarlet tangle]

so js const but2 = new MessageButton(); now js const but2 = new ButtonComponent();

[vague coyote]

thats... what the guide says, yes

[scarlet tangle]

we need to change this to js const { MessageActionRow, MessageButton, MessageEmbed } = require('discord.js');

[vague coyote]

Obviously, yes

[scarlet tangle]

so i need to do js const { ActionRow, Button, Embed } = require('discord.js');

[vague coyote]

You should prioritize learning JS instead of using an in-dev version of djs.

[scarlet tangle]

what expect day to release discord.js v14 in main version?

[icy dew]

we don't know

it will be released when it will be released

[vague coyote]

its a very early in-dev version

[scarlet tangle]

client.on change now?

[vague coyote]

Please, stop.

[scarlet tangle]

i have dout so i am asking

[icy dew]

doesn't work as well. Throws an error saying embeds[0].color[NUMBER_TYPE_COERCE]: Value "GREEN" is not int.

[vague coyote]

The guide tells you all major changes.

[icy dew]

so int it is

[dark light]

client.on didn't change

[scarlet tangle]

no just last thing is client.on change now?

[vague coyote]

[tame gazelle]

no strings allowed for button style too?

[velvet jasper]

yup

ButtonStyle.X

[icy dew]

or use the magic numbers but i think it isn't recommended

[scarlet tangle]

can i ask you something

[tame gazelle]

ask here ._.

[velvet jasper]

also @tame gazelle strings for intents actually does work, it's a side-effect of us using the bitfield class

[icy dew]

I'm assuming it will be patched soon?

[scarlet tangle]

is client.on change

[icy dew]

oop sorry for ping

[velvet jasper]

don't think so

we'd have to change how BitField works

[tame gazelle]

^

[vague coyote]

all changes are documented in the update guide + vape told you no

[scarlet tangle]

idk what happen on that

[icy dew]

maybe in the guide, add the changes about .setColor() or color as well? I mean it's the same as button styles, so maybe a tip or something?

[velvet jasper]

i don't think a decision has been made about wheter we'll allow color strings or not

it just so happens the /builders version don't support color

[icy dew]

oh, it currently throws an error if I use a string

using JSON

[distant canopy]

.setColor()?

[velvet jasper]

what error does it throw?

[icy dew]

embeds[0].color[NUMBER_TYPE_COERCE]: Value "GREEN" is not int.

but using 0x00FF00 works

[velvet jasper]

yeah I think we're missing a step in serializing the json

[icy dew]

hmm alright

[velvet jasper]

this is what the old code is doing, so I think this needs to be added into the new code

https://github.com/discordjs/discord.js/blob/988a51b7641f8b33cc9387664605ddc02134859d/src/structures/MessageEmbed.js#L402

[icy dew]

ah

[scarlet tangle]

is this right way js const embed1 = new Embed()

[distant canopy]

Looks about right

[tame gazelle]

looks like I've finished that are in the guide
thanks for help

something.hexColor still returns a string

do I have to do Util.resolveColor(someting.hexColor) ?

[finite fog]

Yeah, or you use .color

[tame gazelle]

.color would be better, thanks

[jaunty vault]

is there a reason that Embed is not in docs?

[icy dew]

not added yet ig

[velvet jasper]

it's in the builders docs

[icy dew]

oh

[tame gazelle]

does 0xDD000 still works for .setColor() ?

[jaunty vault]

Embed is part of builders now??

[tame gazelle]

you can import it from discord.js

[icy dew]

should work

[velvet jasper]

it should

[jaunty vault]

what about the other things from builders, can you import those?

[tame gazelle]

dunno

[icy dew]

i use json so idk

[velvet jasper]

you can import message components, and embeds from builders directly from discord.js, they're reexported

[icy dew]

msg.reply({ 
  embeds: [someEmbed], 
  components: [{
    type: 1, components: [
      { style: 1, label: "TestLabel", customId: "testing", type: 2 }
    ]}
  ]
})

this gives me an error components[0].components[0].custom_id[BUTTON_COMPONENT_CUSTOM_ID_REQUIRED]: A custom id is required

[velvet jasper]

try using custom_id instead of customId and see if that works

[icy dew]

yea that works

so will snake_case be the new way to send stuff using JSON?

[velvet jasper]

no that's a bug, if you don't mind can you create an issue ticket so it doesn't get lost

[icy dew]

sure no problem. Should i test this with other stuff as well (message embeds, slash commands and so on)?

[velvet jasper]

if you can that would be greatly appreciated

[icy dew]

alright

[tame gazelle]

the class ContextMenuInteraction has been renamed?

[jaunty vault]

ContextMenuCommandInteraction

[tame gazelle]

thanks

[icy dew]

@velvet jasper hmm if i look at the builder docs, all of them use snake case. Could it be because of that?

[velvet jasper]

possibly

[icy dew]

alright

[icy dew]

I made an issue just in case

[dull mulch]

#7376 in discordjs/discord.js by 3061LRTAGSPKJMORMRT opened <t:1643649229:R>
[discord.js@dev] Using JSON structures do not accept camelCase.

[median jetty]

list of all intent

[vague coyote]

you know the docs exist, right?

okay nvm, docs suck

[median jetty]

No the intents is changed

[vague coyote]

I see

@velvet jasper what happened with the intents

[velvet jasper]

https://github.com/discordjs/discord-api-types/blob/8e13cd80c66d11d93157a053e329ad98ece4a457/gateway/v9.ts#L174

[vague coyote]

ah we had that talk already in internals, nvm then

[median jetty]

and partials?

[velvet jasper]

look at Partials in the main docs

[vague coyote]

they are not linked anymore btw

they are missing?

[plain rover]

Partial
A Partial object is a representation of any existing object. This object contains between 0 and all of the original objects parameters. This is true regardless of whether the parameters are optional in the base object.

[vague coyote]

thats stable

[quick elm]

hawyeah

[icy dew]

yea they aren't linked.

the list of partials i remember are

• User
• Channel
• Message
• GuildMember
• Reaction

i took this from the guide https://discordjs.guide/popular-topics/partials.html#enabling-partials

[median jetty]

The new permission is this

[velvet jasper]

yes

[vague coyote]

siris do you know where partials went

[velvet jasper]

https://github.com/discordjs/discord.js/blob/0803665183f62e5aeb3b708c1bf9cad598cb2087/packages/discord.js/src/util/Partials.js#L13

[median jetty]

before CREATE_INSTANT_INVITE now CreateInstantInvite?

Correct?

[velvet jasper]

yes, PermissionFlagsBits.CreateInstantInvite

[median jetty]

it's required PermissionFlagsBits

[velvet jasper]

yes

[tame gazelle]

strings are allowed for this?

[median jetty]

    Perms: [
        "CREATE_INSTANT_INVITE",
        "KICK_MEMBERS",
        "BAN_MEMBERS",
        "ADMINISTRATOR",
        "MANAGE_CHANNELS",
        "MANAGE_GUILD",
        "ADD_REACTIONS",
        "VIEW_AUDIT_LOG",
        "PRIORITY_SPEAKER",
        "STREAM",
        "VIEW_CHANNEL",
        "SEND_MESSAGES",
        "SEND_TTS_MESSAGES",
        "MANAGE_MESSAGES",
        "EMBED_LINKS",
        "ATTACH_FILES",
        "READ_MESSAGE_HISTORY",
        "MENTION_EVERYONE",
        "USE_EXTERNAL_EMOJIS",
        "VIEW_GUILD_INSIGHTS",
        "CONNECT",
        "SPEAK",
        "MUTE_MEMBERS",
        "DEAFEN_MEMBERS",
        "MOVE_MEMBERS",
        "USE_VAD",
        "CHANGE_NICKNAME",
        "MANAGE_NICKNAMES",
        "MANAGE_ROLES",
        "MANAGE_WEBHOOKS",
        "MANAGE_EMOJIS_AND_STICKERS",
        "USE_APPLICATION_COMMANDS",
        "REQUEST_TO_SPEAK",
        "MANAGE_THREADS",
        "USE_PUBLIC_THREADS",
        "USE_PRIVATE_THREADS",
        "USE_EXTERNAL_STICKERS"
    ]
}```

I use this

for permission validation

is required js PermissionFlagsBits

[velvet jasper]

yes

if it's a bitfield strings are allowed

[median jetty]

?

@velvet jasper

[tame gazelle]

since we can put bitfield for intents, does it mean that we can also put intents as strings?

[velvet jasper]

yes

[tame gazelle]

this is fine?

[tame gazelle]

._.

I'm confused

[vague coyote]

at this moment you can use strings, yes.

you could have tested it

took me 3 minutes to test that

[slim wharf]

What happend with e.g. Discord.Permissions.FLAGS.KICK_MEMBERS. Will it be removed?

[tame gazelle]

already tested and it works

[river harbor]

ah shit... here we go again...

[vague coyote]

already is

[tame gazelle]

but Crawl said that it will be removed so ._.

[river harbor]

time to rewrite my bot...

[vague coyote]

do you have any benefit in using v14, lurker?

[tame gazelle]

me?

[river harbor]

i just wanna be up-to-date

[vague coyote]

this isn't a release

its an in-dev version

[river harbor]

no, but when it comes out i'll need to rewrite

[vague coyote]

that will still take some time

[slim wharf]

I can't understand, whats the reason.

I literally had to change 1000 of lines for v13 to UPPER_CASE permissions.
Now it is being removed, seriously?

With this kind of breaking changes, it is pointless to keep your bot up-to-date with the upstream

[vague coyote]

then dont do it, we use discord-api-types now

and we already used upper case permissions in v12

[woven grove]

Feel free to fork

[jolly pike]

write the bot in typescript, makes upgrading much easier

[slim wharf]

but string at first, then enums, now other enums lol

Same mistake has been done with Application Command types. Its obviously the same thing, string to enum and it was predictable.

[tame gazelle]

you are able to use strings in v13 too

in v14 you will be able too

[slim wharf]

I am talking about permissions.has() , did not accepted a string at v13.

[tame gazelle]

it does

[jaunty vault]

yes it does

[vague coyote]

[slim wharf]

• The v12 - v13 migration guide suggested it.

[vague coyote]

yes, thats the recommended way of using it, doesn't mean its the only way

[jaunty vault]

are builders getting better errors?

[slim wharf]

So now, I have to do PermissionFlagBits.Administrator?

[vague coyote]

Thats the recommended way, yes

[vague coyote]

Not sure if they already implemented it, but yes, they will

[urban belfry]

looks like it hasn't been implemented yet

[slim wharf]

And Discord does not has it on Uppercase?

[vague coyote]

I cant tell you why they switched to how it is now

[slim wharf]

https://discord.com/developers/docs/topics/permissions#permissions-bitwise-permission-flags
They have it as Uppercase.

Plot twist:

v15 changing it back to Uppercase.

I may sound rude, but I do not mean it on this way.

[vague coyote]

SNAKE_UPPERCASE :P

[velvet jasper]

This is because the style for enums for ts/js should be PascalCase

we're following the microsoft style guide for this

[novel notch]

Does anyone know if there is already a discord.js v14 guide?

[balmy ember]

Yes, it is linked in the pinned messages

[novel notch]

Thanks

[dawn phoenix]

Q: What happened with Intents?
A: You can import the GatewayIntentBits enum from discord-api-types https://github.com/discordjs/discord-api-types/blob/8e13cd80c66d11d93157a053e329ad98ece4a457/gateway/v9.ts#L174

Q: What happened with Partials?
A: You can import the Partials enum from discord.js https://github.com/discordjs/discord.js/blob/0803665183f62e5aeb3b708c1bf9cad598cb2087/packages/discord.js/src/util/Partials.js#L13

[plush monolith]

Hey, I understand your point, but on the other hand. Discord.js major version comes out every year or so, and you make so many major changes that I think are sometimes unnecessary. Wouldn't you like to take a slightly different tactic? I'm sure you wouldn't want to keep rewriting it either. For example, there was RichEmbed, then MessageEmbed, and now there will be Embed. Ok, that's enough just replacnut but there are also changes that require manual rewriting.

[median jetty]

events?

[vague coyote]

events didnt change

[velvet jasper]

There’s more reasons than just a consistent style, I’m going to make a discussion on gh explaining the reasoning for all of these changes beyond aesthetics

[plush monolith]

Okay, then send link please

[velvet jasper]

https://github.com/discordjs/discord.js/discussions/7380

[novel notch]

Someone knows how to put the buttons I get the error TypeError: MessageButton is not a constructor

[urban belfry]

it's now ButtonComponent
https://deploy-preview-1011--discordjs-guide.netlify.app/additional-info/changes-in-v14.html#messagecomponent

[novel notch]

Thanks

[flint bough]

v14 already??

[vague coyote]

its still in development

isn't like thats what the first pin says

[knotty plover]

And the category name

And the channel name implies it

[vague coyote]

and the fact that the guide is a deploy preview

[dawn phoenix]

Q: Why are you changing "X" for "Y"?
A: https://github.com/discordjs/discord.js/discussions/7380

[woven grove]

Spoiler: because we can

[novel notch]

How can I search in the guide that the search engine does not load anything

[vague coyote]

Weird, agreed, doesn't work.

[dawn phoenix]

The deploy preview has probably been built before some breaking internal changes, so the search keys are still outdated

[novel notch]

Then someone can pass me the section of embed and buttons please xd

[vague coyote]

https://deploy-preview-1011--discordjs-guide.netlify.app/popular-topics/embeds.html#embed-preview but not yet updated

https://deploy-preview-1011--discordjs-guide.netlify.app/interactions/buttons.html#building-and-sending-buttons same goes for buttons

[novel notch]

Thanks

[shadow plume]

ow my a lot of changes yay

[novel notch]

I left to send an embed but without color xd

[stray ferry]

what is this?

[scarlet tangle]

Read the pinned messages

[gusty pier]

guide seems to have conflicting info - it mentions both EnumResolvers#resolveButtonStyle and EnumResolvers#buttonStyle

[stray ferry]

ok

[icy dew]

You can use both. Some people want to use strings so they use EnumResolvers#resolveButtonStyle("PRIMARY")

the other one doesn't use an enum resolver, it just exports ButtonStyle. That is there so you can use ButtonStyle#Primary

[sly narwhal]

so dumb btw

[knotty plover]

🧂

[icy dew]

look at the pins if you want to see why it happened. Obviously no one wants to rewrite thousands of code, but they have to change it for consistency so that it's easier to spot bugs and actually not make the code hard to maintain

[sly narwhal]

will read

[undone yew]

how to fix?

[tame gazelle]

check the guide

in the pin

[undone yew]

I couldnt find it

[icy dew]

I'm assuming channel.type will also return a number right?

so we would have to do if (<Channel>.type === 2) right?

or use the enum resolver

[pliant salmon]

Use enum resolver probably

channel.type should return what the api returns to you, so or it returns a string or djs itself implemented the enum resolver inside the type function

[icy dew]

so if (<Channel>.type === <EnumResolvers>.resolveChannelType("DM"))

or would it be Dm

[pliant salmon]

W8 lemme check, bcz i think you can just do "DM"

[icy dew]

I think it would Dm since they are changing from SCREAMING_SNAKE_CASE to PascalCase

So GUILD_TEXT becomes GuildText

[pliant salmon]

Idk, i just woke up saw the "news" abt djs v14 and im going to start converting stuff now

But im pretty sure channel.type will still return a string

[icy dew]

@velvet jasper Hey, sorry for ping but https://discord.js.org/#/docs/discord.js/main/typedef/ChannelTypeEnumResolvable still uses SCREAMING_SNAKE_CASE, is it supposed to be like that or is it suppose to be PascalCase

[icy dew]

docs didn't state ChannelType yet, so idk

[undone yew]

my code;

const { MessageEmbed } = require('discord.js');

         const embed = new MessageEmbed()
          .setTitle("Something went wrong...")
          .setDescription(`Sorry, you have **blacklisted** the bot by its \`Founder\` or \`Developer\`. You cannot use the bot's commands. `)
          .setTimestamp()

          return interaction.reply({ embeds: [embed], ephemeral: true})

[icy dew]

it's Embed now

[undone yew]

uh, thx

[pliant salmon]

use the enum resolvers

[icy dew]

yea using that rn

[icy dew]

ah

knew it

[tame gazelle]

numbers so?

[icy dew]

so either magic numbers or enum resolvers

[icy dew]

iirc you can use numbers, but if discord changes it, you will have to implement the changes yourself. If you use EnumResolvers, then you won't have to change anything

[pliant salmon]

@icy dew just import ChannelType from djs and do like so

[icy dew]

Oh yes that

[pliant salmon]

this should fix your problem without enum resolvers

[tame gazelle]

EnumResolvers would be better but does discord.js calls the resolver internally?

[icy dew]

but shouldn't it be ChannelType.Dm? or ChannelType.DM? DM is an acronym right?

[pliant salmon]

caps

i mean, if you use vscode intellisense should do it for you

[undone yew]

MessageButton and MessageActionRow Did it change?

[icy dew]

Yes

[tame gazelle]

ActionRow and ButtonComponent

[icy dew]

- const button = new MessageButton();
+ const button = new ButtonComponent();

- const selectMenu = new MessageSelectMenu();
+ const selectMenu = new SelectMenuComponent();

- const actionRow = new MessageActionRow();
+ const actionRow = new ActionRow();

[undone yew]

thx

[icy dew]

ah alright, and no I don't use vsc

I have it, but it's gonna take years to load so forgive me if you hear me saying this, but I am using good ol' Notepad

[pliant salmon]

xd

are the activity type changes listed on the changelog? 🤔

[icy dew]

idts

i mean only this thing changed:

- new ActivityFlags()
+ new ActivityFlagsBitField()

[pliant salmon]

yeah i mean the activity type

[icy dew]

yea it isn't listed then

[pliant salmon]

they also changed that to enum but i didnt see it properly mentioned

[icy dew]

lmao

we could just use Channel.isDM()

instead of channel.type === "something"

[pliant salmon]

if isDM returns a boolean then there is no need to call it

but the code for it would literally be the same

[icy dew]

ye i mean if only we found this earlier

all methods btw

[pliant salmon]

the only reference i could possibly find about the changes in the activities is here (screenshot) but i think this should be listed anyways

[icy dew]

yea

Most stuff isn't documented yet, and is subject to change, so we'll just have to wait ig

or notify one of the contributors or smth

[pliant salmon]

i mean, im fine bcz of vscode i just think that it should be documented for anyone who starts

[icy dew]

pretty sure it's in their to-do list

yup

[undone yew]

how to fix?

[pliant salmon]

its what it says on the error, you are sending a string instead of a number

also, that doesnt look like a djs error

but maybe try to look at this

[undone yew]

There was no such thing before the discordjs error v14.

.setColor(ctx.config.color.default)

[icy dew]

your embed color has to be an integer.

[icy dew]

yea, this is a string

[undone yew]

how to fix?

[hazy vine]

[icy dew]

use Util#resolveColor()
https://discord.js.org/#/docs/discord.js/main/class/Util?scrollTo=s-resolveColor

[undone yew]

Do I need to send numbers?

[pliant salmon]

yes

[undone yew]

.setColor(resolveColor(ctx.config.color.default))

true?

[icy dew]

you need to import Util

[pliant salmon]

also, there is other thing missing on the documentation for v14, just leaving the note here that dynamic got removed

[undone yew]

how?

[icy dew]

so ```js
const { Embed, Util } = require("discord.js")

const embed = new Embed().setColor(Util.resolveColor("GREEN"))

[undone yew]

thx

[pliant salmon]

why not use hex??

just .setColor("#00FF00")

[icy dew]

it only accepts an int

[pliant salmon]

or if you prefer setColor(0x00FF00)

[icy dew]

according to docs

[icy dew]

yea i use this

[pliant salmon]

its the same

[icy dew]

int !== string

[pliant salmon]

0x00FF00 === "#00FF00"

[icy dew]

nope

[pliant salmon]

both represent hex values

[icy dew]

but the type is different

[tame gazelle]

the second one doesn’t work

only 0xyddhdjz

[pliant salmon]

did they also change it?

[icy dew]

yes

[pliant salmon]

bcz using #00FF00 used to work

[pliant salmon]

welp thats pain

[icy dew]

it's not listen in change logs

[pliant salmon]

that explains it but also doesnt make sense

[pliant salmon]

it used to be

lemme see smtg

[icy dew]

at first i was confused, until someone said to use util.resolveColor in this channel

if you want RANDOM, then use util.resolveColor

[pliant salmon]

na

i think im fine,
biggest part of the embeds i use just grab the color from the user

[icy dew]

ah, then you should be fine

[pliant salmon]

yeah

• i have my own fromHex function if needed

but i will take a look at djs one just for curiosity

[undone yew]

uhh

[pliant salmon]

use the enum values

[undone yew]

how?

[pliant salmon]

where you are creating the buttons

[icy dew]

use EnumResolvers for button styles

[pliant salmon]

create them with the new enums instead of "PRIMARY" and stuff like that

[icy dew]

^

[undone yew]

context.js

[pliant salmon]

thats one of the main changes

[icy dew]

either import ButtonStyles and do ButtonStyles.Primary

[undone yew]

database of buttons

[icy dew]

or import EnumResolvers and use EnumResolvers.resolveButtonStyle("Primary")

[icy dew]

hmm, the guide shows caps

[undone yew]

it looks better

[tame gazelle]

'cuz it's in caps

[icy dew]

ye, mb i thought it changed

Because it's ButtonStyle.Primary

so i thought it should be the same with resolveButtonStyle()

I think something isn't intended

[pliant salmon]

bcz it is caps

the old way was also caps

[icy dew]

then why is it ButtonStyle.Primary

why isn't Primary in caps?

should I ask in #archive-library-discussion

oh one uses discord-api-types and one is from djs itself

[undone yew]

Does this little make a big difference?

[icy dew]

they do the same thing.

[tame gazelle]

<Message>#type is a number now?

[undone yew]

so it can be big or small

[icy dew]

ButtonStyle.Primary or EnumResolvers.resolveButtonStyle("PRIMARY")

[icy dew]

for caps, use EnumResolvers, for the other, use ButtonStyle

mb

[tame gazelle]

how can I display <ChannelType>#type as string?

[pliant salmon]

bcz thats a function and the other is a string, even tho it doesnt make sense thats developer choice

[pliant salmon]

wdym?

[icy dew]

Property actually

[tame gazelle]

<ChannelType>#type returns a number right?

[undone yew]

const SECONDARY = EnumResolvers.resolveButtonStyles("SECONDARY")

can it be used like this (by definition)

[icy dew]

idk, i just use <Channel>#isX()

[icy dew]

should work

[tame gazelle]

it's for channelinfo command ._.

[pliant salmon]

actually i havent logged it but it should since they moved it to enum

[icy dew]

they import ChannelTypes from discord-api-types, so i assume they return numbers

[pliant salmon]

even tho idk why they did that bcz if you compile enum from ts you can use both number and string

so it doesnt make sense to me the route they went

[tame gazelle]

I want strings (also we can import it from discord.js)

[icy dew]

not all ppl use ts

[pliant salmon]

the compiled version tho

[icy dew]

oh

[icy dew]

idk

if we do resolveChannelType(2), will it return a string?

[undone yew]

new error

@icy dew do you know?

[icy dew]

how are you putting your emojis?

[pliant salmon]

like...

[icy dew]

so both return numbers

[pliant salmon]

yes

[pliant salmon]

thats why they could keep string, and if its string you index it to the enum

[icy dew]

your emoji has to be a raw object

i.e client.emojis.cache.get(config.emoji.button.delete)

[undone yew]

config

[icy dew]

and so on

[undone yew]

will i use this?

[icy dew]

yes

[undone yew]

okay

[pliant salmon]

can you show the code?

[tame gazelle]

the error said that it's line 79

[rain bramble]

Shouldn't it be { name: "name", value: "value", inline: true }?

[tame gazelle]

isn't that for .addFields() ?

[icy dew]

they changed it

[tame gazelle]

._.

[undone yew]

AA

[pliant salmon]

addFields its Array<APIEmbedField> while addField its only one

[icy dew]

show code

[undone yew]

using customId:

[icy dew]

it's custom_id: now

[tame gazelle]

array of objects?

[pliant salmon]

yes

addField: { name: string, value: string, inline: boolean | undefined }
addFields: [{ name: string, value: string, inline: boolean | undefined }]

so instead of spamming addField you can just create a bunch in 1 function

[tame gazelle]

yeah but I add fields in a if statement ._.

[pliant salmon]

its valid to just do addField a bunch of times

[tame gazelle]

I do that

[pliant salmon]

but its redundant

thats why addFields exists

[urban belfry]

that's not how it works
it should be type: 1, components: [....]
what you have is the completely wrong format
again, show your code

[pliant salmon]

ofc if you use if statments to define them there isnt much to do

[undone yew]

It works, but the buttons do not work

if(button.customId == 'delete') {}

[icy dew]

it's button.custom_id now iirc

[pliant salmon]

fr?

[undone yew]

v15: Embed => MessageRichEmbed .D

[icy dew]

yes https://discord.js.org/#/docs/builders/main/class/ButtonComponent?scrollTo=custom_id

[pliant salmon]

welp i havent messed with buttons for a while

[icy dew]

welp time to refactor my code

i think all camelCase properties for classes in builders will be changed to snake_case

[pliant salmon]

at least the only thing i had to change in my client was the DM type and interaction isCommand

[icy dew]

yea

[pliant salmon]

commands will be the problem

[icy dew]

i mean vsc has find and replace

shouldn't be that hard

[pliant salmon]

it isnt

[icy dew]

you just press enter all along the way

[pliant salmon]

but some of my bots i do not maintain anymore so i gotta ask the current coder to learn how to do that bcz he uses webstorm

the only thing im rly wondering is if people rly use the collection functions

[undone yew]

still not working

[icy dew]

show how you are doing it

[pliant salmon]

can you show your code?

[undone yew]

            system.on('collect', async (button) => {
        
              if(button.custom_id == 'delete') {
        
                interaction.deleteReply();
        
                await button.deferUpdate();
        
              } else if(button.custom_id == 'previous') {...}

where error?

[icy dew]

hmm, that returns a ButtonInteraction

[pliant salmon]

maybe wrap it in a try...catch to see the error?

[undone yew]

no errors

[tame gazelle]

it doesn't take an array

[icy dew]

can you log button.customId

[undone yew]

Interaction failed error occurs when pressing the button

[tame gazelle]

it takes an object too

[pliant salmon]

then reply to the button bcz i dont see where interaction is defined

[pliant salmon]

wdym?

[tame gazelle]

.addFields() doesn't take an array

[pliant salmon]

it does

[tepid narwhal]

"await interaction.deleteReply()" normaly ?

[icy dew]

what?

[tame gazelle]

wrong reply

[icy dew]

are you using .addField or .addFields?

[pliant salmon]

fields is not field

[tame gazelle]

I know

[tepid narwhal]

Oh okay, thx

[undone yew]

to where

[icy dew]

in your event just now

[tame gazelle]

and I get this error ^

[pliant salmon]

oh, remove the []

they added ...

[icy dew]

bruh

[pliant salmon]

undocumented changes

[pliant salmon]

not documented, you can see on my screenshot they added ...

[icy dew]

yea, i guessed it

[pliant salmon]

now you can just do it without the []

[undone yew]

not working

[pliant salmon]

which is pain

[pliant salmon]

can you console.log(button)?

[pliant salmon]

doesnt djs have a format timestamp option?

[tame gazelle]

for?

ah Formatters?

[pliant salmon]

yes

[tame gazelle]

I've never used it

[pliant salmon]

idk

i think they have something but im not sure

they do

https://discord.js.org/#/docs/discord.js/stable/class/Formatters?scrollTo=s-time

[scarlet tangle]

discord.js v14 !?

[vague coyote]

its an in dev version

[dawn phoenix]

unsure what you expect as an answer to that query

[scarlet tangle]

what features will have ?

and what happened to v13 guide

[vague coyote]

all you need to know so far is pinned

[scarlet tangle]

not https://discord.js.org/

I remember there is a another site explaining think better

[dawn phoenix]

nothing happened to the v13 guide, it's still the deployed version of https://discordjs.guide/

[scarlet tangle]

oh that one i was searching that tysm

[dawn phoenix]

also linked here

[scarlet tangle]

ok

[pliant salmon]

i think this should be addressed asap

3 lines with that error on djs types

[undone yew]

I did but there is no movement in console

[dawn phoenix]

then it doesn't even reach that point of your code

[undone yew]

what could be the problem?

[dawn phoenix]

hard to say, try to find out where your code stops execution/differs execution wise from what you expect

[pliant salmon]

Souji, should i open a issue about the types?

[dawn phoenix]

i have no idea what's going on there, but i did update a bot yesterday with the recent at-dev release and did not encounter any errors

[undone yew]

I can't find any buttons are not working

[dawn phoenix]

and how are we supposed to find it then?

[pliant salmon]

it isnt giving any errors with what im using but someone might have issues + djs types shouldnt have any errors

[undone yew]

I think it doesn't send custom_id?

Definition:
button.customId

Button:
custom_id

Interaction failded

[dawn phoenix]

what is "button" even?

[undone yew]

i don't know

[dawn phoenix]

then find out?

[undone yew]

My context (includes buttons) file

what is the problems?

help

[vague coyote]

are WE supposed to debug your whole code now?
No thanks 💀

Thats still your job

[tame gazelle]

the dynamic option has been removed?

for avatar

[vague coyote]

its now forceStatic

set that to false

https://discord.js.org/#/docs/rest/main/typedef/ImageURLOptions

kinda weird that its on rest now 🍣

[undone yew]

No, just the buttons don't respond

I couldn't find the problem

[tame gazelle]

thanks

[undone yew]

if(button.customId === 'last')
          ^^^^^^^^ 

What should I write here?

[vague coyote]

what is button

[undone yew]

            let fetch = await interaction.fetchReply();
            const system = fetch.createMessageComponentCollector({ componentType: 'BUTTON', filter: (clicker) => clicker.user.id == interaction.user.id })

            system.on('collect', async (button) => {

              if (button.customId === 'delete') {
        
                interaction.deleteReply();
        
                await button.deferUpdate();
        
              } else if (button.customId === 'first') {...}

[vague coyote]

log button

and show the output

[undone yew]

button didn't respond to it either

[urban belfry]

wait it's still going to be called MessageComponentCollector?

[vague coyote]

[undone yew]

what will i write?

[vague coyote]

log button
and show the output

[undone yew]

.

[vague coyote]

explain that

[undone yew]

you know not answering

[urban belfry]

no, even i don't understand what "button didn't respond to it either" means exactly

[undone yew]

No movement in console.

no output

these were working fine without custom_id, when I did v14 customId started giving error.

if(button.customId === 'delete') {...}
          ^^^^^^^^

I just don't know what to write here

[urban belfry]

@undone yew import ComponentType from discord.js and access ComponentType.Button instead of this componentType: 'BUTTON'

[undone yew]

ComponentType.Button or componentType: ComponentType.Button ?

which one will i write

[urban belfry]

the latter of course

[undone yew]

thanksss

workedddd

where error?

[finite fog]

The stacktrace tells you what method you used and where you used it, the error tells you what was expected and what was received.
I'm not sure what more you'd need.

[undone yew]

i don't know

[icy dew]

something needed a string, but you gave undefined

[pliant salmon]

yes

already talked about that here

[vague coyote]

setAuthor takes an name option, not content
addFields takes multiple field objects, not an array

[urban belfry]

so the docs for addFields is wrong too?

[vague coyote]

yes

[pliant salmon]

outdated but yes

[icy dew]

question, is it just me or does anyone else get FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory

never got this in v13, but i get this in v14.

could it be because i have multiple setTimeout or smth

[undone yew]

What do I need to change on addFields?

[pliant salmon]

remove the []

we where talking about that idk how you didnt see it

[velvet jasper]

Will fix

[pliant salmon]

i will open a issue for the types

[icy dew]

nvm it's probably because of my system

[tame gazelle]

didn’t read

[pliant salmon]

npnp

they didnt document that yet so its normal

[vague coyote]

it is documented, just not in the guide

[pliant salmon]

not on the changes they posted both on the guide preview and the github v13 -> v14

[vague coyote]

with documented I mean discord.js.org

if you click on imageurloptions in the docs, it directs you to the proper page

[pliant salmon]

ah yes

but there is no information that it got changed thats what i meant

[vague coyote]

Yes, but you should always look at the docs if you get a problem like that anyway

[pliant salmon]

and its rare for me to go to the docs since i have all directly on my ide, thats how i found the errors in the types

[pliant salmon]

i didnt look, just ctrl+click on the type and i saw why xd

[vague coyote]

just to clarify, you changed yours to forceStatic, right?
Not that you think it got removed

[pliant salmon]

i didnt change bcz forceStatic now its true by default so i just deleted it

[vague coyote]

wut, its none by default according to docs

[pliant salmon]

rly?

w8 a sec

this is what i saw

[vague coyote]

ah okay

idk, should say false, none confuses

[pliant salmon]

true now its the oposite of the dynamic: true (?)

[urban belfry]

if we use dynamic as an example, by default now it's dynamic: true

forceStatic: true would be explicitly saying dynamic:false

[pliant salmon]

Yes

Thats what the guide suggests at least

[vague coyote]

forceStatic is made false by default, so I think the type should be changed too
https://imageing.eu/shared/dGYFf0Y.png

[pliant salmon]

Its on the name

ForceStatic forces the url to be the static one

So having it to true is the same as dynamic: false

[vague coyote]

well yes, saying its none by default is not correct tho

it doesn't matter really, but I think showing it default false in the docs is cleaner

[pliant salmon]

I didnt see none tbh

[vague coyote]

https://discord.js.org/#/docs/rest/main/typedef/ImageURLOptions

[pliant salmon]

Thats true

But that maybe happened bcz the type is forceStatic?: boolean or forceStatic: boolean | undefined

Docs maybe got confused with that

[urban belfry]

it doesn't mention @default false
unlike MakeURLOptions.extension

[pliant salmon]

Yeah, and for what im aware the docs arent made by hand so it got confused

They can change that ez but its not smtg that will break your code

[gleaming parcel]

whats gonna change with v14?

[slate mango]

Many things, please check pins

[undone yew]

        const button = new ctx.Discord.ActionRow(
            new ctx.Discord.ButtonComponent(
                { name: "Boy", style: ctx.Discord.SUCCESS, emoji: ctx.client.emojis.cache.get(ctx.config.emoji.OptionalEmojis.AccountUser), custom_id: 'boy', disabled: false }
            )
            
        )

where is error?

[pliant salmon]

Check the pins

[vague coyote]

register js line 116

[undone yew]

const button = new ctx.Discord.ActionRow(...)

[urban belfry]

oh no sory

[vague coyote]

since when does ActionRow takes a buttoncomponent in the constructor

[urban belfry]

it doesn't

it takes an apiactionrowcomponent, which has a type property and a components array

@undone yew pass nothing to the constructor and use addComponents

[icy dew]

they were being sarcastic but ok

[undone yew]

😑

[urban belfry]

well.. what is fetch?

[undone yew]

fetch = interaction.fetchReply();

[vague coyote]

prooommiiissseee

[plain rover]

Tag suggestion for @undone yew:
Resources to understand Promise:
• MDN: learn more
• Guide: learn more
• JavaScript info: learn more

[pliant salmon]

await moment

[undone yew]

-_-

[pliant salmon]

oh, im actually curious now

does djs have any plans to support ESModules?

[urban belfry]

@undone yew you're being difficult, that error's not telling us much, show us the code if you want someone to be able to answer you

[urban belfry]

instead of passing an object, use the builder methods

like ButtonComponent.setLabel('something')
also this is a good time to mention, content?? button.content?

[vague coyote]

lmao

also addComponents doesn't take an array afaik
same as addFields in an embed

[undone yew]

:D

working, but buttons not work

[vague coyote]

also addComponents doesn't take an array afaik
same as addFields in an embed

[urban belfry]

but setComponents takes an array of components

[vague coyote]

yes

[urban belfry]

whereas setFields takes a rest parameter

[pliant salmon]

thats a change that i still dont understand

[urban belfry]

i understand not wanting to support multiple types of input, but they should be consistent
i'd expect setFields and setComponents to be consistent

[undone yew]

bruh

[urban belfry]

again, you're not showing code

[pliant salmon]

they used to be...

thats a v14 change for some reason

[urban belfry]

well they aren't now 🙃

[undone yew]

no code errors