#djs-in-dev-version
1 messages · Page 2 of 1
Python is probably one of my most hated languages, I hate it, so I have not seen it no 🤣.
Yes, according to some people, creating functions to change a function is an anti-pattern, because it changes what that function does, and makes it harder to understand, or some other stuff they said, idk.
Though it's nice to see in PHP8 they now have decorators 😄
I can understand an issue with mixins, decorators imo don't change a function, they just augument how it's used
But that's getting a bit off topic haha
I mean, you can literally change what a method or class does entirely.
I do agree there 🤣
To sum up basically what I've spent the past hour talking about, DJS should look at deno as a way to support more recent web standards, and then backport this into node, even if some of it requires polyfills to work in node, as I reckon web standards are the way to go, even on the server. Node support is still essential however, as there's just such a big community around it and djs on node currently
Also look into wasm instead of native modules
</rant>
Definitely agreed, would love to see discord using rust or something under the hood (like Prisma) 😮
Native modules are just a pain to get working on some platforms, wsl and arm can be problematic, as it needs to be recompiled for every platform, but I digress
I need to get ready to leave for uni, good chat @shy willow
And you, enjoy!
I'm confused as to why web standards are relevant to what discord.js is though. A server side API wrapper
Or what rust/prisma has to do with... anything here
i dont get why people like it
its like to simple and the syntax is stupid
who tf is saying python is one of the most hated languages
No one I don't think.
everyone
Neither, I always look it, and I am aware that I am the problem in this, but I look at it as like "my first language" 🤣 I am sure it's a good language, but syntactically, I hate it 🤣
We were discussing the pros and cons to ESM/CJS and Deno/Node, based on the most recent announcement! 🙂
Fair enough
Apologies if there is a better place to have this discussion, but I couldn't find anywhere, and this channel, seemed somewhat relevant due to it being a suggestion.
Isn't Prisma a orm for sql
Yes
Yep
Yes its bad
We aren't dropping Node support
Why not
Because it would be super fucking dumb
djs is a main language or it's library from JavaScript language.
It's a library written in TS and JS
i'm just seeing a general push for some of the more recent web standards, even with nodejs, WHATWG fetch being added directly into nodejs being an example
this is probably more of a personal opinion than anything too, but i feel like it just makes sense that rather than having say, nodejs specific buffer, and request / response apis (for http servers), we may as well already use the standardised apis that exist on the web for both front and backend
thats the part of deno that i like
and thats why i think embracing deno as a potential (additional to nodejs) target to write code for, could be an interesting idea to discuss
especially as nodejs seems to be moving this way at the moment too
completely up to you guys which way you go ofc, this is just my take on the whole backend javascript situation (also note that i haven't actually done too much server side javascript in the past year or so, so i could be missing a bit of context)
Pretty sure most of the users here uses Nodejs and do not have any intention to move to Deno soon, which actually doesn't seem to have so many advantages
why when i run yarn build it shows it can not install zlib-sync and i have this log?!
It literally tells you what you’re missing (about 10 times)
https://github.com/discordjs/discord.js/issues/8563
If I made a branch for this issue, what would i start it with? fix/, feat/, or something else?
Technically a feat, since it wasn't intended to be a typeguard originally
does anyone know how can i actually solve this issue? or even catch this, it results in some of my shards requeing or becoming of zombie connections
How do I check if the authorization I entered is in the bot?
What is dev version btw
its the version that is actively being worked on for future versions?
No, it’s not a release, so no number assigned
on npm it says dev is 14.3.1
Hello, I have been a bit off since february, and I was searching about select menus being added on modals during this time and it seems so, but I can't find any info on how to do it, am I wrong? or where I can see an example? Couldnt find it on discord.js.org
select menus on modals are not a thing yet, not in djs and also not on discord
Oh, thanks, then it was mb reading ;_;
Hey guys, hope this is the right place to ask this question. I'm attempting to fix an issue in /ws and I'd like to build and test it out. I figured out how to build it from the docs, but I'm unsure how to move my changes over to the project where I'm testing the changes
Might be a good idea to make a post in #992669226403909652 about the issue? Then you can elaborate on it
Will do! Thank you
Nightly build, whats that
built by all-nighters ig
discordjs dev build
Lock channel
you think "nightly build" is a clear name?
yes, actually
Yes?
djs-canary or djs-dev-branch
Built every night, at night time, nightly
How long does it usually take for PR's with not much change to be reviewed?
Like?
wdym like?
#8565 in discordjs/discord.js by MaksiRose opened <t:1661682166:R> (review required)
feat: add typeguard to BaseInteraction#isRepliable
This I figure?
for example, but i was also just asking out of curiosity
@discordjs/docgen:build:
@discordjs/docgen:build: ERROR: command finished with error: command (packages\docgen) yarn run build exited (1)
command (packages\docgen) yarn run build exited (1)
why!!?
so where i put failOnWarn: false because i put it in build.config.ts it shows it doesn't exist?
Wdym it doesn't exist?
it has typescript error
If you run the test script do you receive the error? Or you just see it in the IDE?
no it is the ide that the failOnWarn it is not in the function already
so can you show example how can i put it , bec i think i put it wrong
You should've changed only this
Np
what does mean by blocked?
That it cant be merged yet
lol
do you mean nobody can approve the changes or what?
and what is the reasons for that
Approving changes isn't merging, usually, but in our case we have auto merge. This label disables the auto merge
hiii
can anyone help me with a bot im making? 😄
it is a fork from github so the repository is available if that makes it easier 😄
#archive-offtopic , this channel is for discussion of the nightly built development version of djs
thank you!
Why you still don't add description to your PRs? Iirc this was discussed here before, describing what are you doing is essential to any project/PR
https://discord.com/developers/docs/change-log#sessionspecific-gateway-resume-urls
I saw this a few weeks back, not sure if it is implemented in discord.js-
No, but it's in /ws
Ahh
Was slightly concerned since it does disconnect my bots more often, hopefully it reaches stable branch soon
That shouldn’t be in effect yet, starting September 12th
Got it
afaik we can't just randomly replace current ws with /ws in the main lib
also, assuming reconnections count towards identifies, it would have to reconnect you every 90s or more often for that to be of any concern at all.
which i heavily doubt would be the case.
👀 Is there a reason that a lot of the API types are marked as type exports only in the typings, when they're actually available as enum imports in plain JS?
Probably because DJS export them natively and the types are just for docs, but idk
They're not just for the docs though, you actively consume them for checking types of things 🙂
Docs I mean the autodocumentation of vscode too
Hey guys, should my bot's client id be the same as guild id?
it's not
1015734069931294812 <- This is copied ID with developer setting on
copied from where
and this is client id from application window on discord applications
server where the bot is
yeah but where exactly
uhm, on my private server? I don't know how to answer this differently
what do you right click to get the id
soooo, the copied id is the same as the one here?
where's the issue?
shouldn't guild id and client id be different?
but when are you even getting guild id
Shouldn't the guild id be the ID I copied from this message?
like
you right click message, you copy message id
not channel, not guild, not user, not role, not command or virtually anythign else.
What website?
how should I get the guild id automatically when the bot joins a new server?
well, that's a question for #djs-help-v14 or #archive-djs-help-v13
Hi, so I opened a pull request recently (https://github.com/discordjs/discord.js/pull/8565) and Jiralite reviewed it saying that InteractionResponseFields seems to no longer be referenced anywhere. Now some tests failed, because it is actuall referenced in index.test-d.ts. Below are the pictures for this. Would these three references just need to be replaced with the new RepliableInteraction type that I introduced to replace InteractionResponseFields?
The problem is that InteractionResponseFields was an interface and RepliableInteraction is a type, and I don't know exactly what this code does, so I'm not sure how to properly fix this.
Looking into tsd, expectAssignable should need a type, so just replacing it with RepliableInteraction would be right. I hope i'm not breaking anything
Replace and test again, if the tests pass I think there will be no problem, but I'm no contributor so idk
i don't know how to test again. pushing it, it doesn't test again automatically for the PR because for first time contributor, a maintainer needs to do that
Run yarn test on the project root, it will test all packages iirc
@jovial cypress Follow the Setup on the contribution Guide: https://github.com/discordjs/discord.js/blob/main/.github/CONTRIBUTING.md
Empty?
Are you sure your code follows that exact route?
or that receivedQueueData doesn't return a promise
i don't understand
is receivedQueueData an async function?
Without full function code neither can I
yes
but I'm not used await
i fixed thanks
this channel is for d.js contributers?
if yes can i request a functionality
just asking dont be offended 😓 😓
make a post in #992669226403909652
I would prefer djs in bun
and why are you telling me that
"sry for ping" when you could literally have just not pinged
@knotty plover sorry for thw ping, but pong
We should talk in #archive-offtopic instead
I've seen a lot of issues related to shads disconnecting and not reconnecting anymore in the last, I've read that could be memory not beeing available and I'm not sure about it, I've also read about it could be related to the new reconnect logic using local specific ws. I'm sending this here looking for other opinions about it
Some post I foud related to it
(Maybe this should be a post on #992669226403909652 )
well it was the same issue for me they would turn into zombie connections this might be a issue with the memory i had some shard arguments for it and it seemed my memory was exceeding and then shards would go down to fix this i couldn't migrate to a better vps or try to solve discord.js memory usage since djs has lots of validations i might break so i instead increased the shard count more than the gateway recommends and now that seems to fix it for many guilds i still face it but with a less amount of unavailable guilds
there are pull request has been 1 month and no one from maintainers made any reply or anything!
and 2 pull requests has been 1 week
for example?
You mean, 3 of your prs that still lack a proper description and explanation
ok but no one said in the PR that can not understand the explanation !!
And tbh, all of your prs have a milestone set on them
Meaning that in a future version they could be implemented
So be patience
ahaa ok , understood now
All of these have their last action a week ago, which of them is the one you mean has been ignored for a whole month?
wdym "understand the explanation" - there is no explanation
You ignored the PR template on all 3 entirely
i said there is one pull request has been a month
what if we do the collection and caching in discordjs by c++ instead of javascript, it will be very fast
And how do you plan to have discord.js do that in C++ instead
so we can use node-gyp in that
And you think that will be faster than having native hashmaps
ofcourse, you can try by yourself
because big bots that in thousands of servers it will need cache it all and will be very slow, but if we did by c++ it might be very fast
No no I want you to try it
i tried to cache big things but not in discord js in c++ normally and there is very big diffrence in performance
discord.ts?
it is very small thing to increase performance only
I still dont know what you're basing this on
You want us to develop an external hashmap package using node-gyp and C++ to increase in-memory storage performance?
the bridge from js -> native is way slower than storing in js
Even though the V8 runtime Javascript/Node natively uses is written in C++ anyway
that's why your cache is slow Monbrey - have you considered rewriting the v8 runtime in rust to get better cache performance?
Thats so 2021, we write runtimes in Zig now
Bun is 🚀 BLAZING FAST 🚀
i just suggest this idea
You sure did
What about hash maps in zig instead of rust
rust is not easy in coding
Yeah C++ is much easier
yep
yeah that's why c++ is slow compared to rust
zig is good and it is syntax very simple and very fast
I love C++ templates!!!1!
and there is something called carbon made by google it is syntax like kotlin and has same speed like c++

but the performance it is the most important thing for the big projects , that's why nodejs has c++
Yes but I dont think you understand anything outside that single statement
ofcourse it is not easy to do and you will change many things
i know that
Thats not what I mean
This is what I mean
It doesnt work how you've assumed it works
mhmmm ok
guys why is LimitedCollection in discord.js instead of @discordjs/collection
More context?
i wanted to import LimitedCollection from @discordjs/collection but only discord.js exports it and i dont need the whole discord.js package for my project man
It's an extended class that's used for discord.js primarily in conjunction with sweepers. For example, LimitedCollection#keepOverLimit would not make sense in that package. It would do nothing
Similar to LimitedCollection#maxSize - not sure how the utility package @discordjs/collection would define that property
i used it wrong then because i dont use sweepers lol
What do you use it for then?
I thought you can use them like normal collections but with limited size
we dont use jest though
We could mock the REST (gatewayBot) request to force the ws to use an localhost url
And use a normal websocket
Will try to find a vitest alternative
I will open a forum post
Finally, all the prs of 7791 have been merged
#7791 in discordjs/discord.js by suneettipirneni opened <t:1649824263:R> (review required)
feat: add support for guild forums
Poggers
Incredibly poggers
Probably a dumb question but, whats the use of the lazy() functions on djs?
iirc importing optional modules at runtime
To reduce memory usage?
to not crash when the module isn't installed
and not have some weird workarounds
But it is used to get internal structures too 
const getCategoryChannel = lazy(() => require('../structures/CategoryChannel'));
It also handles circular imports
sup folks, does anyone know if this guide https://discordjs.guide/ aim for discord.js v14 or v13 ?
14
you can access the v13 guide at https://v13.discordjs.guide
thanks!
Oh, amazing
I presume messages will be postable / editable in forum threads once the lib is updated? the FAQ says bots cannot do such things
the faq doesn't say that "bots cannot do such things". it just says that currently d.js doesn't support forums
A GUILD_FORUM channel is very similar (from an API perspective) to a GUILD_TEXT channel, except only threads can be created in that channel; messages cannot be sent directly in that channel.
I understood it wrong, thank you
Should https://discordjs.guide/additional-info/changes-in-v14.html#messagecomponent mention Discord.Modal -> Discord.ModalBuilder?
Ty, I will make a pr
Should anything be mentioned about now having to write
- new Discord.MessageActionRow()
+ new Discord.ActionRowBuilder<Discord.MessageActionRowComponentBuilder>()
// or
- new Discord.MessageActionRow<Discord.ModalActionRowComponent>()
+ new Discord.ActionRowBuilder<Discord.TextInputBuilder>()
MessageActionRow -> ActionRowBuilder is mentioned but not the type changes
guide is made for js afaik
you forgot new keyword before Discord.MessageActionRow() Discord.ActionRowBuilder<Discord.MessageActionRowComponentBuilder>() and Discord.ActionRowBuilder<Discord.TextInputBuilder>()
yes I did, thank you
it is mentioned here https://discordjs.guide/interactions/buttons.html#building-and-sending-buttons
but not in the changelog i suppose
I have another (potentially stupid) question
EmbedAuthorOptions https://discord.js.org/#/docs/builders/main/typedef/EmbedAuthorOptions doesn't list out the actual properties it has. It'd be nice if it did.
Clicking on EmbedAuthorData indicates it's IconData & Omit<APIEmbedAuthor, 'icon_url' | 'proxy_icon_url'>
But APIEmbedAuthor isn't linked, so it's not obvious at all what properties are allowed or what they are called
Is there a way to changes this / would it be worth changing?
when I try and get all members in a text channel the bot only returns me and the bot IDs, not everyone in the channel. Any ideas on why it's not returning everyone?
const channel = interaction.member.guild.channels.cache.get(interaction.channelId);
channel.members.forEach((member) => {
console.log(member.user.id)
})
fetch all members
and move to support channel bc it's not related to dev
Is the need to use GatewayIntentBits.MessageContent new in v14?
u can even use bot without any intents so no
v14 uses v10 of the gateway/Discord API, where the MessageContent intent is enforced
thanks
Of course, but my question is predicated on needing to read message content
what event is fired when a forum post is archived
threadUpdate
are this available in discordjs? https://discord.com/developers/docs/resources/channel#crosspost-message
crosspost message
Message#crosspost()
Publishes a message in an announcement channel to all channels following it.
wait wrong thing
lol
what?
i am wrong 
https://discord.js.org/#/docs someone broke the docs
What's broken?
I do not have that issue. It's likely a problem with you
make it possible that you can use images that you use in the bot that you can use them as avatars
I'm not quite sure what you're asking - it's already possible to set the bot's avatar using discord.js
ClientUser#setAvatar()
Sets the avatar of the logged in client.
oh sick i didn’t even realise that existed
If you do it you need to use avatarURL so u can't use a photo file that is in the bot
No, that accepts local images. Filepaths are buffer resolvable. The example even shows that
When u use webhooks
That one is a Discord limitation I believe, it cannot accept files
iirc it accpets the avatar data in base64
Creating or Editing a webhook does, setting avatar on send doesn't
ForumChannel (extends GuildChannel)
Represents a channel that only contains threads
I don't know where to direct this so but its related to you guys so
https://www.sapphirejs.dev/docs/Guide/getting-started/getting-started
This link is broken
On the page you linked, there is a GitHub button. Click it and raise an issue there
👍
Also where did you get that link from?
https://www.sapphirejs.dev/docs/General/Welcome
Scroll down to Links and its the guide
Pushed a fix. Once Vercel has deployed it, it's fixed.
👍
I opened an issue here https://github.com/sapphiredev/docs/issues if you wanna close it
wait I can close it nvm
Oh well docs is also not the correct repo fyi. That only has autogenerated files (similar to discordjs/docs repo). The guide pages are in the website repo.
in index.d.ts, theres a lot of ChannelTypes mentioned that don't exist anymore. Can't find the AnnouncementThread one at all anymore, others like PublicThread have been renamed to GuildPublicThread. Should I open an issue?
your discord-api-types version is outdated
how do i update it?
running an install should do it
yarn
The errors still exist sadly
a window reload fixed it
im trying to do yarn test but it crashes my pc
i think it uses too much RAM
i got it working now but im not sure what im supposed to do with this error message. where in the builders folder do i look for the error?
there should be more info above? prefixed with @discordjs/builders:test
does it happen consistently? have you tried running the tests again?
no because my PC completely freezes for a good 10 min or gets unresponsive entirely
is there a reason why ForumChannels don't include the nsfw key?
#8662 in discordjs/discord.js by Jiralite opened <t:1663796733:R> (review required)
fix(ForumChannel): Implement missing properties and methods
perfect tysm 👍
why <ThreadChannel>.parent can't return ForumChannel https://discord.js.org/#/docs/discord.js/14.4.0/class/ThreadChannel?scrollTo=parent
It can
I am literally making a pull request for that as we speak - it's just not documented nor typed to
whenever i try to commit on my local repo rather than the virtual workspace, this happens. any ideas why?
Ur pre commit hook is trying to use yarn, but it isn’t installed
well if i just used yarn test wouldnt that mean that yarn is also installed
isnt this for v14.4.0?
this is for the development for djs in general
oh ok
Can I help develop djs?
yes
Ok
Had some trouble install vscode 😐
so why all this errors and i didn't make anything in the files
so how when i make a commit it will test discord js only not all packages!!
how can i do this
@still shadow
what is the code for send a embed with my bot? without /commands
this channel is specifically for the 12h at-dev release, please use other support channels for v14/v13
in the collection of discordjs can we batching keys together instead of adding keys one by one
that will increase performance of caching
i know i mean we should create an object instead of using Map() this will be breaking changes
we should find a method to increase performance of caching, because it kills the memory and the bot will set long time to start
bec, v15 we want it have good performance
This aint it chief
If memory is your concern, the problem is the amount of items in cache, which is why we allow caching behaviour overrides
The TypeScript rewrite is also looking into ways to reduce the size of the actual objects, more raw data storage and getters rather than large classes
ok but if it has enough memory it will set for long time
like if bot in 1m server
i think more than 1 billion data will cache
Not if you configure the cache
Besides, what does that have to do with changing a Map() to a far-worse performing object?
Please read the link I provided
ok we shouldn't change to object we can change to another thing or find a method, it is a complex thing at anyway
If you can find a more performant key/value lookup than the native Map, sure
yeah we should increase performance of it
Like I said, if your concern regarding caching is memory consumption, the solution is simply to cache less things
It doesn't matter what structure they're cached in - do it less, and make the objects in the cache smaller
Which is already a goal of the TypeScript rewrite
yep
there are another thing we should do
we should make less functions
i saw that discordjs has a lot of functions and that will decrease performance
I really have to wonder what you're basing this on
Yeah a library that doesnt do anything is very performant. The problem was functionality all along! Doing things is slow, doing nothing is instant!
i want discordjs fast and easy in using
ofcourse , but we can find method that has less functions and easy in use
there is a solution ofcourse
anything has solution
so yeah how can i find the design of discordjs?
Not when you're inventing the problem
wat do you mean?
Collection is already an buffed (it extends) Map bc it needs more functions to make life, development and UX better
Go for it
so, how are you going to lookup elements from the array based off of the key?
💀
Hi I have this issue with the bot where I gave him all of the GateawayIntents needed and when inviting him I gave him administrator perms=8 but I still get this error for trying to change usernames
This is how I define my client
how to learn discord js
Wrong channel you 2
where shall i ask
In the support category like everyone else
Ok?
It’s still not better
What performance lol
done
Inserting items?
and now lookups are O(n) 
Inserting items is a one-time deal usually. You aren’t inserting a million items constantly
No, reading is O(1)
How faster would it be lol
there really is nothing to explain
you don't seem to understand the fundamental idea of a hashmap
It won’t need fast inserting items
or whats actually slowing down your bot's startup
It also won’t insert 100 million of items
which is namely gateway connections, which you can get like, 1 every 5 seconds
It’s not 100 million still
And what do you save by this? 1-2s when starting your bot?
All of this for 1s?

You aren’t making sense
In summary, no, literally nobody agrees
discord.js is not a framework, something like Sapphire already exists to make that easier
() => (message) => message.author.id === message.client.user.id The double function is intended in the sweeper options?
Bc that's how the types define it
// How it is
export type GlobalSweepFilter<K, V> = () => ((value: V, key: K, collection: Collection<K, V>) => boolean) | null;
// Shouldn't be
export type GlobalSweepFilter<K, V> = ((value: V, key: K, collection: Collection<K, V>) => boolean) | null;
Yes that’s intended, so you can have time-based filters like the built-in lifetime filter that gets Date.now() in the outer function to make sure each filter run uses the same timestamp to compare against (but not every sweeper run does)
Or even use values fetched from database or whatever you want to influence the current sweep run
from a bot dev perspective anyone know how the dyno custom pfp works or any other similar bot, probot/moo6 etc? does it create a new shard bot instance for every server that wants one?
not even shard, it needs to be a custom bot, which requires the end user to pass you a token to use, as there is an application limit
i - too this day - have no idea how mee6 gets away with this. generally tokens should not be advised to share with other people
apparently being famous helps
Oh so they run the bot on your app token? Wow lol

That also seems like it circumvents verification requirements for being in that many guilds 
the same way they wouldn't if it wasn't a "custom" instance
what requirements though 
If people are providing their own tokens, for applications that are only in a single guild, there's no verification needs for applications running on that token to have access to GuildMembers, GuildPresences etc
I mean Mee6 is probably verified anyway of course
oh, limitations, not requirements
Yeah thats probably what I meant
Is there a change log for what is ** actually new** in dev version from stable ?
Commit history, yes
I think you got the thing other way around (14.5.0..main)
Edited
What's the best way to "bump" a pull request that hasn't been reviewed yet? Is it better to just wait?
Iirc, pull requests are organized by id so generally it won't be possible to bump a PR without re-opening it
You probably won't get a faster review
Maintainers usually find time to go through and review everything pending for them at once, not just some bumped one
👍
updatePlayerCount: (client, seconds) => { const interval = setInterval(function setStatus() { status = “status”
The status = “status” is deprecated
I can’t find the updated version could someone point me in the right direction?
Sry if this is the wrong channel for this question
how can assigning to variable be deprecated
It says status is deprecated. ts(6385)
It works but I just don’t feel safe using deprecated stuff in my code
well, because it looks like you're trying to assign to this https://developer.mozilla.org/en-US/docs/Web/API/Window/status
why is there no "syncId" in the Activity class anymore, even though the sync_id is being sent by the gateway?
idk if it is
probably not
#7844 in discordjs/discord.js by almeidx merged <t:1650925845:R>
refactor(Activity): remove undocumented properties
discord.js doesnt support undocumented features
@rigid haven can u apply this: https://github.com/discordjs/discord.js/pull/8559#pullrequestreview-1133376675
its merge ready then
Does discord oauth support some kind of events? I want to be notified when someone changes their username or profile picture
nope
you can fetch their profile every now and then when they use the site
¯_(ツ)_/¯
I guess most people who use my website are prob gonna also be apart of my discord server
could use it in combination with a bot I guess
seems a bit much for such a thing
Yea
they wont have the website open all the time will they
just re-fetch their profile when they visit the site
ah
making it so they can login with discord oauth
hmmmmm
Would prob be smart to have a bot
cause than I can make the oauth only work if they are in my dsicrod server
but then you have reliance on it
exactly
I guess
wont get weird people registering on my jellyfin
true
does v13 @Dev have forum support?
v13 has a pr for backporting forums currently in progress
#8651 in discordjs/discord.js by aiko-chan-ai opened <t:1663764294:R> (review required)
feat: backport guild forum support to v13
👍
Version 14 already has it, just a fyi
done
By the way, why are the form fields always set to "Required" by default? I don't really find it logical when the slash command builder doesn't set the options to "Required" by default 🤔
I do, because TextInput get always shown to the user, while slashcommand options only appear if you explicitly select/type them in your chat input. Not saying that's the reasoning behind it, just that that's my stance on it
Oh okay, I see
As making pr
how to use it with https://github.com/discordjs/discord-api-types/pull/602 ?
#602 in discordjs/discord-api-types by advaith1 opened <t:1665697008:R> (changes requested)
feat(Components): new select menus
iirc npm i lets you install directly from GitHub
as testing okey
but what in pr
hm?
You can install the branch ig
Select Menus V2 will be a breaking change?
Yeah I think so. discord.js SelectMenuBuilder probably will be changing its name to align with the new selects. I'm guessing it would change to something like StringSelectMenuBuilder
Maybe discord.js can implement it without changing its name until v15
yeah i added StringSelectMenuBuilder but SelectMenuBuilder is still left
but i still cant install the api-types
SelectMenuBuilder will be an alias?
It's still left, but deprecated
^
For me, I got it using:
git clone -b new-selects https://github.com/advaith1/discord-api-types.git ./node_modules/discord-api-typescd ./node_modules/discord-api-typesnpm inpm link
For some reason, npm does't know how to install the branch
git clone -b new-selects https://github.com/advaith1/discord-api-types.git ./node_modules/discord-api-types && cd ./node_modules/discord-api-types && npm i && npm link This should work on bash
Is someone already working on the new selects?
Yeah
When will v12 be disabled?
Soontm
When API v6 will be disabled
It kinda already is broken, it can't support text-in-voice
When select menu types?
Whenever someone makes it
...
Does djs support the automod events yet?
#7983 in discordjs/discord.js by suneettipirneni closed <t:1654120406:R>
feat(webhook): add support for creating forum channel posts
mhh missspell
#7938 in discordjs/discord.js by Jiralite opened <t:1652824011:R> (review required)
feat: Auto Moderation
^ so it's in progress
Alright
yea but honestly v14 isnt that useful
atleast imo, bc all it has rlly is forum support and renamed classes and functions
plus from what i can see in #announcements v13 is still maintained
while true, it won't be maintained forever. additionally, it's using API v9 as opposed to v14's v10, which inherently means earlier drop from discord's side (assuming they don't decide to have any v10 exclusive features)
is there a pr for new select menus yet
im working on it
I think you should open a draft pr so that people know about it on the discord.js github (and wait for discord-apt-types to include them soon)
That's not a bad idea
when @rigid haven will make tests
ping
or I will know how to typeguard it as normal
Wdym typeguard it as normal
btw it has been merged: https://github.com/discordjs/discord-api-types/commit/df1452dc28f2fddb32a20912ca3ca3634556a3da, just need to wait for it to be released onto npm
to let .componentType work
but w/e
when i go on BaseOptions: https://discord.js.org/#/docs/discord.js/main/typedef/ClientOptions
and then click on RESTOptions, i get this:
https://discord.js.org/#/docs/rest/main/typedef/RESTOptions
is it supposed to be empty?
docs :/
https://discord.js.org/#/docs/rest/1.0.1/typedef/RESTOptions
changing version will work
Just need to explicitly type the “type prop” for each select menu type
the thing is that we want to make one class
uhh, but they arent the same
What mon said they each have different resolved data fields
I wouldn’t advise making them one class but instead having be a part of the same base class
Wouldnt they just be new classes? What would you be breaking?
okey
Where is this piece of code handled in v14?
In /rest, why?
but where exactly? i can't find it
the reason why is kind of complicated but it relates to #1021512891385532506, I talked about how I never had ECONNRESET errors before but ever since switching to v14 I get them all the time. I actually found one single instance of getting an ECONNRESET error before, and instead of just pointing to node:internal/stream_base_commons like all the newer ones do (and yes i could confirm that these errors originated when making a rest request to discord, like interaction.reply etc), it pointed to this exact line of code. except, this is v13.8 and not v14.x, so i would like to know how this is handled in v14
okay, so here's my train of thought:
if a rest request (like interactions.reply) is leading to an ECONNRESET error, but with a non-existent stacktrace other than node:internal/stream_base_commons, where before the only time this occurred it did actually point to this place in the code, it makes me feel like this error is not actually getting caught. so instead of djs counting retries and then throwing that HTTPError after some time, it is not even retrying because something gets hung up somewhere. I would have to dig deeper into the code to really know if what im saying even makes sense here, but that's the only way this makes sense to me
Hmm I've not experienced an error like that before in the post
well, im experiencing it all the time right now. the issue is that i updated bot 1 to djs 14, and only ever since have this specific error daily. meanwhile, bot 2 is running without ever having that issue.
few weeks later, i update bot 2, now it has the same issue
my other bots who are all still on djs 13 do not experience this issue
i am really confident that this must have something to do with djs 14, otherwise i have no idea how it could go from never occurring to occurring daily for two bots independently from each other starting at the day that i update it to djs 14
@uncut kelp I tried looking into how request (L308) works, but i'm not entirely sure:
When would an error be thrown and caught by the catch block (L309) vs when would it return Dispatcher.ResponseData?
In the old version, it called request.make() which came from the APIRequest class which used node-fetch. I didn't find a reference to undici which is where the request in the new version is called, so something changed there i guess and i don't know how different it is.
point is, in the old version, any failed request would be treated the same, giving it some retries before calling HTTPError. In the new version, caught errors only get retried if it is an AbortError, and once done, it just throws the raw error rather than using HTTPError (L316).
And apparently failed requests (like status 500) don't cause a rejected promise, but rather go through an then get caught with an HTTPError when necessary (this is the line you provided to me)
So, what is the likelihood that because in line 316 a raw error is thrown rather than it being packaged into an HTTPError object, that this is where the ECONNRESET problem that I am having originates? If so, then a second issue arises, namely that this error never gets retried, meaning that if there is a connection issue once, it will just stop working, rather than retrying in case the connection issue has resolved
And then this would explain why this issue suddenly starts popping up this much for me: Maybe the connection of my provider is just spotty enough to sometimes cause a split second connection issue, and with v13 I never noticed this because it would just retry and then work. And in this version, it skips the retry, which makes that error appear far more frequently
And assuming that I understood the code correctly here, would this be considered a bug? Since in cases like mine, where retries prevented this error from appearing basically ever, the lack of retries in the new code means that the error appears more often. So it would be cool if another if-case was added that would ensure retries were performed before giving up
And also maybe it would be a good idea to transform the error into an HTTPError or something to ensure an accessible stack trace is added
undici request is significantly lower level than fetch, though fetch and request should only fail in the same places. The only time request fails (outside of an abort error) is due to a system error, most of which should absolutely be fatal to the request cause there's no chance of recovery. ECONNRESET is kinda interesting in that it often is recoverable (and something I often special case). Additionally, the stack direct from the error should be more meaningul than anything we construct at that point, so I'm unsure what you mean there
TLDR: Throwing the caught error there is the correct behavior because the error occurring is not an HTTP Error, however, ECONNRESET should be special cased. I'll make a PR
To implement the ephemeral deleting, is removing https://github.com/discordjs/discord.js/blob/main/packages/discord.js/src/structures/interfaces/InteractionResponses.js#L167 the only thing that has to be done?
and in a semver major should the propety be removed or kept as can be useful in some usecases
Already in a PR
or sorry
Which property are you referring to?
the .ephemeral
That's being kept, doesn't hurt to have
The Error constant is being removed though
Its technically major but will probably be released as a patch since it's a bug fix to an upstream major
👍
thanks for the reply 🙂 (and sorry for not checking for a pr again- checked a while ago but only commented now)
No problem
#8774 in discordjs/discord.js by monbrey opened <t:1666309772:R> (review required)
feat: allow deletion of ephemeral messages
making a special case for ECONNRESET would be amazing. I have my own recovery system in place too now due to how frequently this kept happening for me, but having it in djs natively would really save some trouble
can you notify me when you made the PR so i can enable updates for it and know when it got merged and stuff?
and the thing i meant with the stack trace is that my ECONNRESET error basically doesn‘t have a stack trace other than node:internal. That means that it is really difficult to pinpoint exactly where it comes from. I guess it is not necessary to make a more meaningful stack trace, though.
Have you tried logging it using console.trace?
yes, thats the only reason why I know it comes from discord.js erroring on methods like interaction.reply. Did you read my whole text earlier?
it starts here: #djs-in-dev-version message
I'd like some opinions here
https://github.com/discordjs/discord.js/pull/8773#discussion_r1001164364
I'm wondering if it should actually go in the options. If so, would it be a new type name, or just an intersection type? If it's a new type name, what should it be?
Also, if it's going into the options, would it make sense to do the same with the Webhook methods?
Since it would be a breaking change I think we should leave it as a separate parameter for now and move it to the options in v15 or TypeScript rewrite with other parameters that should be moved to.
What about the options in the pr? It wouldn't be a breaking change in that case
I think we can move it and create InteractionEditMessageOptions type
It would also be weird for the other methods that would get this change
for example, fetchReply({ message }) or deleteReply({ message }), despite it being the only argument
What Message Components are allowed in a modal?
only text inputs for now
thanks!
it’s pointless 🗿
#8774 in discordjs/discord.js by monbrey opened <t:1666309772:R> (review required)
feat: allow deletion of ephemeral messages
what’s the point in deleting ephemeral responses when you can just dismiss them
i don't think this is the place to discuss that? maybe you can open a ticket @ https://dis.gd/contact if you want them to remove it
nah i have nothing against it, just confused
it's changed API behaviour, it will be added in a patch or minor release, although technically breaking
if it makes sense or not is indeed irrelevant, you can do it, d.js will support it
eg message that should be shown to one user for a time
I'd like to report an unexpected behaviour in v14.5 stable version
interaction.member.permissions.has("ADMINISTRATOR") works when the user has admin permission but crashes when it doesn't. I believe it should also crash when the user has the permission as a different method such as interaction.member.permissions.has(PermissionsBitField.Flags.Administrator) should be used.
You should make an issue
This was the error I received:
node:events:491
throw er; // Unhandled 'error' event
^
RangeError [BitFieldInvalid]: Invalid bitfield flag or number: ADMINISTRATOR.
at PermissionsBitField.resolve (/Users/jiralite/Documents/GitHub/Caelus/node_modules/discord.js/src/util/BitField.js:168:11)
at PermissionsBitField.has (/Users/jiralite/Documents/GitHub/Caelus/node_modules/discord.js/src/util/BitField.js:60:28)
at PermissionsBitField.has (/Users/jiralite/Documents/GitHub/Caelus/node_modules/discord.js/src/util/PermissionsBitField.js:92:82)
at Client.<anonymous> (file:///Users/jiralite/Documents/GitHub/Caelus/sourceJS/14.js:11:29)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Emitted 'error' event on Client instance at:
at emitUnhandledRejectionOrErr (node:events:394:10)
at process.processTicksAndRejections (node:internal/process/task_queues:84:21) {
code: 'BitFieldInvalid'
}
As far as I can tell, nothing seems amiss here. What error are you getting?
Yeah that's the expected error
but it works when the user actually has the administrator flag
I cannot reproduce that. The error above is returned on administrators and non-administrators.
so it only becomes valid if the user has the flag
weird. Maybe it was a 14.5 error that got fixed in 14.6
Actually the error indeed does not happen when checked on administrators - had my permission check-up wrong there
So would you consider it unexpected behaviour in order to open an issue on github? (I would)
No
Its probably just because of how checkAdmin works
https://discord.com/developers/docs/topics/permissions#permission-overwrites
Discord's pseudocode here demonstrates how it should be handled
I think it ignores input and checks for Administrator and returns true
I mean it should at least warn the user that they are checking the permissions wrong
If you turn the checkAdmin option off it'll probably still error
So should I report it (or anyone else, I don't care) or just ignore it?
any updates on this? :)
heyoo
I have an stupid* question here 🙂
can we get the roles that a user has on a different discord guild? where my bot is not in
working on it today
amazing :D
#8785 in discordjs/discord.js by ckohen opened <t:1666697930:R> (review required)
fix(SequentialHandler): downlevel ECONNRESET errors
@jovial cypress
great, thank you! let's hope this gets added to the 14.7 milestone :D
its a subpackage, so it could be released sooner than that
ohh true. Well, the sooner the better for me!
what is this channel used for can anyone explain ?
Discussing the development of discord.js or seeking support in using the in-dev version
ok
Would it be possible at any point to do things such as fetching/editing/sending a message without having the channel be fetched? Aka do it via the channel id?
fetching a message without having the channel be fetched, correct
Client#rest
The REST manager of the client
And use /types to get the routes
was about to say, using rest is not really that nice because it doesn‘t provide all the features discordjs does such as typings etc
You would have to manually instantiate the structures
for example, if i want to edit a message, and i want to edit the components specifically, discordjs won‘t do that conversion stuff for me. i have to make sure everything works myself, and possibly miss a bunch of edge cases and introduce bugs when discordjs literally has everything in place already, just requiring a channel object where it isnt necessary
Builders exist
again, it is a lot more work than just having a built in method for it
why not just have that? it would be much more safe in terms of bugs and stuff
and it would require less API calls
You can prob make a partial text channel yourself
wdym
also ^
my main issue is that i feel like it could make things unnecessarily buggy. yalls rest stuff isn‘t very well documented either
Bc d.js was designed to be object oriented, not functional
when i asked about rest in #djs-help-v14 i got sent away. so basically, im not getting any form of support for this, basically no documentation, and its not added natively either
that doesn‘t mean there can‘t be functional programming in there when it saves API calls
it‘s not like its just for convenience. it‘s for a valid reason, saving both me and discord resources
while feeling safe that it will not introduce critical bugs due to a lack of knowledge/understanding
what am i supposed to do with that? it gives me two examples and then thats it
2 examples isnt docs
You want a guide for rest?
docs !== guide
i dont want a guide
Well, the docs tells you the methods on the Rest class
i want docs, but two examples isn‘t docs. for example, i tried finding out what it will return when i get channelid/messageid. it‘s an ApiMessage object, but i didnt find any documentation about this
And I think it’s fairly straightforward. rest.put(route, restOptions)
and its not typed
Correct, its not
That’s why we have -types
I wouldnt know where to look on how to create a message object from that that just misses the channel object but is otherwise functional in terms of the .edit function etc. And since even just asking for the type is apparently outside of the scope of this server, how am i supposed to find that out without any docs on it
but then a doc that would have the types for each endpoint would be good right?
? can you elaborate
discord-api-types.dev
discord-api-types provides all of the types used by Discord for ws and rest
REST is a basic HTTP wrapper around the API, not a fully typed interface
Thats what discord.js is
You're expecting the high level QOL that discord.js provides while trying to use a lower-level wrapper
thats why i don‘t understand why discord.js, a fully typed interface, doesn‘t have a function to fetch, edit and create messages without having to fetch a channel first when it‘s not required by the API and would save on API calls
It does
what would that be
what do you mean?
It doesnt have that because its object oriented
channel.messages.edit exists to allow you to edit messages without fetching the message
.
Its not built for functional programming, no
But a pure REST wrapper is not designed to be fully typed
exactly, i‘m not asking for rest to be typed
im asking for that object oriented wrapper to have some functional programming where it makes sense due to it saving API calls
i just want to save API calls, not end world hunger
Thats not the design paradigm though
The way to save API calls would be for the channels to be in cache
Thats how discord.js is designed
i always thought functionality is more important than design
Then I disagree
You cant throw whatever functionality you like at something and compromise the design in the process
well if you never need the channels then caching them means making unnecessary api calls
A - you clearly do need it
B - theyre cached by default if you have the Guilds intent, Discord sends all the data for them in the initial payload
A - for what though?
B - that depends. if i just started up my bot and i want to resume some functionality from the previous process, i don‘t necessarily have gotten the channel yet and therefore have to fetch it when i wouldnt have to otherwise
whats wrong with a client.messages collection that allows you to do also do edit and fetch and send and all that jazz?
Massive bloat keeping that many messages in another place
or rather object which has cache + those things
We've done a fair bit to try to remove that sort of double-caching
it feels like if something is designed in such a way that a useful functionality isn‘t implementable in any way that follows the design, then the design is flawed
I mean this is one example but there are probably dozens of others. We can't start implementing shortcuts on Client for every route that takes multiple parameters
Just so you dont have to fetch the first one to then make a call for the second
If you want more direct access to the API, thats why REST is provided. REST is that lower level shortcut to do whatever you want
But you seemed to have an issue with that too
im having a massive problem with having to fetch channels especially at bot startup where it wouldn’t be necessary and i am going to have to resort to having to write my own little solution for it but it feels like im not getting any support here for no real reason.
You're getting plenty of support and arguing with every solution provided because its not precisely what you wanted to hear
Are you not caching channels, or doing something that cant wait until the ready event has fired?
my issue is that i
- werent allowed to ask what type i get from a rest request in here, apparently
- didnt really feel like i had access to appropriate documentation
- and as a result don‘t really know how to implement this myself without introducing a whole lot of bugs for no reason
no im restarting my bot
if you were told by "random people" in #djs-help-v14, then most likely they are clueless and just seen that you didn't ask about discord.js directly
so you can mostly ignore that, and it definitely wasn't "not allowed"
And these things must be fetched prior to the ready event?
Yeah there is a problem with dumbasses jumping at every possible opportunity to send people elsewhere instead of using their brain, I'll agree with you on that
no, im just having a bot that has several things it will start resuming when the bot is started up and i want to optimize the process both in terms of speed as well as in terms of resources
so instead of waiting couple seconds for discord to send you the channel, you will instead fetch the channel and complain that you have to fetch the channel?
seems suboptimal
why would discord send me the channel after a couple of seconds? what channels is it sending, why, and how do i know which channels it is sending?
because you just restarted the bot and it is in process of identifying?
but why would it send a bunch of channels
which means that discord will send you all guilds, their channels, roles, permissions and a bit of members?
If your bot has the Guilds intent
it does
The identify payload it sends you includes all guilds, channels and roles
Everything will be cached
Thats how the initial gateway connection works
interesting. then i guess i just need to move stuff around to make that work
personally i thought channels were cached when events like messageCreate and interactionCreate were fired
Sorry if I wasnt clearer on that earlier when I was talking about design. discord.js is a more memory-heavy library compared to some others because of its caching, but thats the design that allows for you not to have to make as many API calls
The channel is already cached (except DMs, theyre an exception), but we do cache the message, user and member when we receive their data with those events
okay, well that‘s good to know. i have disabled much caching where i absolutely do not need it but i don‘t disable channel cache for obvious reasons. i didn‘t know it was provided with the ready event, but if that is so this resolves my issue as long as i just do it after the ready event
how can I do a role reaction pls, thanks for your help
#djs-help-v14 #archive-djs-help-v13 depending on your version, your question is not related to the in-dev-version, is it?
how can i now the version ?
npm ls discord.js
Hey, was told I should bring this here
Is it intended that the default functionality of escapeMarkdown() changed in 14.6.0? (https://github.com/discordjs/discord.js/pull/8701)
Before, escapeMarkdown("test_name"), would return test_name
Now, it returns test\_name
Intended: probably not
known: yes
fix: pass {escape: false} as second parameter (which should‘ve been the default in that PR but wasn’t)
Do you know if it's likely to be reverted? (at least the likely unintended part)
I would assume so, but you can make a PR yourself for it if it‘s urgent for you.
I'll leave it to the pros, I know far too little about that 😅
I'll make a PR as soon as I finish my lunch
@rigid haven can you ping me when you create the PR? I'm currently hard-coding "escape: false" in my project but will remove once your PR is merged
ah yes
@steel haven @marsh matrix @shrewd aurora https://github.com/discordjs/discord.js/pull/8798
Thanks for the notification!
Thanks!
Am I right in thinking that the role and channel select menu builder will come in the next d.js update?
also there is user and mentionable menu
but yeah
#8775 in discordjs/discord.js by jaw0r3k opened <t:1666362502:R> (changes requested)
New select menus
Yes i dont want to tell all of them .
ok
k
will djs v15 store cache data ids in bigint?
uses way less memory also like presence stuff statustype
as a bigint status type so you can resolve it like with permissions?
I think it's better to ask in #992669226403909652.
This is current dev version support channel.
But I don't think that's going to happen. Discord send it as a string and users already use it in their databases as a string, so this would be biggest change in discord.js
Status type is string bc that’s what Discord uses for presence.status
It would add unnecessary complexity internally, similar to how channel.type was before v14
It also doesn’t make sense to make status a BitField bc it’s not possible to have multiple statuses at once. At most, you can have it in different devices but that’s handled differently
Status can be an enum
It is an enum
But as strings, he wants it to be a number or a bigint
Maybe I misunderstood what they meant by their second statement
resolve [status type as a BigInt] … like with permission
Yea, we alr have a string enum for status type
I alr addressed why making it a number/BigInt isn’t feasible
presence.status return a string not a number that's what im talking about
such things you could save as a number or bigint or smt like that
and then u could do stuff like StatusType enum
why though
to save resources
It’s at the cost of internal complexity
ok
Basically the same problem as channel.type did before v14 fixed it
Honestly doesn’t save that much
when trying to run the dev version i get the following error in the file

I have answered in #djs-help-v14.
Add the @dev tag when installing
uninstall @discordjs/builders, it is already installed by default in discord.js
But not in the dev version
ah
still the same
weirdly enough i dont even use that file
You don't, discord.js does
Run npm why @discordjs/builders
You cut off the rest of the output
seems like the dev version of djs does not depend on the dev version of the other packages, you can use yarn resolutions or npm overrides
i have no clue how to 
yarn:
"resolutions": {
"@discordjs/builders": "1.4.0-dev.1667347887-5152abf.0"
}
npm:
"overrides": {
"@discordjs/builders": "1.4.0-dev.1667347887-5152abf.0"
}
in my main projects package.json or the one of discord.js
your file
does dev version have the new select menu types, like role channel?
yes
I NEEED IT lol, how do i install it
npm i discord.js@dev, as said in the topic of this channel
THANK YOU SO MUCH!!!, and sorry to ask but wheres the docs on it 😄
https://discordjs.dev/docs/packages/builders/main/ChannelSelectMenuBuilder:Class
https://discordjs.dev/docs/packages/builders/main/MentionableSelectMenuBuilder:Class
https://discordjs.dev/docs/packages/builders/main/RoleSelectMenuBuilder:Class
https://discordjs.dev/docs/packages/builders/main/StringSelectMenuBuilder:Class
https://discordjs.dev/docs/packages/builders/main/UserSelectMenuBuilder:Class
I think that's all
did you have builders installed separately
Idk, this is my package.json****
you shouldn't have rest or discord-api-types installed separately
ah, then how?
it comes with d.js
still geting that err
do i remove "discord-api-types": "^0.37.16" ?
yes
o
it comes with d.js
so you don't install it separately
still same issue
as far as I can tell this is because we needed to make changes to builders, and while theres a dev release of that as well, it seems our mainlib dev releases don't depend on the sub-pkg dev releases, if that makes sense
tldr the d.js dev release you are using doesn't depend on the needed dev builders release
hm.
its an issue with our release cycle; it's not something you can really fix
we need to look into it
cc @woven grove
cc?
o..
You can just use resolutions
thats quite a hack though 
what? sorry
couldnt we find a way to just make this work
Not a hack really
Using dev can def require that
Not all packages will be ready for release all the time
wait
Just check pins
so what do i do
o ok
add that to package.json?
put it in a row
yes
kk
try it ._.
works
how do i get the role the user picks?
interaction.roles will be a collection of the roles selected
wdym?
exactly that?
is there any examples? or is it just console.log(interaction.roles)?
yes, that should log a collection of roles
kk
thanks @jaunty vault ❤️
same
@jaunty vault it logs "undeined"
interaction.reply({embeds: [embed], components: [actionRow]})
const collector = interaction.channel.createMessageComponentCollector({ componentType: ComponentType.SelectMenu, time: 15000 });
collector.on('collect', i => {
i.reply({ content: `This select menu isnt for you!` ,ephemeral: true });
});
collector.on('end', collected => {
console.log(interaction.roles)
});
did you mean i.roles in the collect event? I'm guessing that interaction isn't the select menu interaction
i.roles wont reply?
what do you mean?
I didn't say that?
what do you mean then?
You are using the wrong interaction object
you should get the role select menu interaction from the collected parameter in the end event
well collected is a collection
so then how?
you can use collected.first() or something else
Collection
A Map with additional utility methods. This is used throughout discord.js rather than Arrays for anything that has an ID, for significantly improved performance and ease-of-use.
kk
why this color not green xd
did you try restarting your ide
no
discord.js is not responsible for your editors language server/theme
that is assuming you're using the right dev versions
also when i click on somthing it doesnt do i.reply
because your filter isnt right
seems like you're not using the correct componentType
ah
ComponentType.RoleSelectMenu ?
RoleSelect
kk
👍
why im getting this error as soon as i start the bot in dev version
read the pin
umm, i read and i didn't understand anything
i had it too
unlucky
add it to package.json
what should i do
...
like this
yes
why?
im getting same error
well i dont know.
These are things you really should be able to know/do if you intend to use code that isn't verified and ready for a stable release
you should probably not use in-dev versions if you can't tinker around - this is not release-ready plug&play - that's what stable releases are for
Who are you talking to?
i got it
me @ebon sleet or?
unlucky, i will wait :/
everyone that applies to, really
o okay!
if you want things to just work™️ - indev is not the version for you
well when will the new version come
when it's ready
when it's ready
Think that's dev version release
but it show 2016
o 2016 lmo
that's when @dev releases from the #main branch
ah ok
it's about time, not date
ok thx



works for npm
