No types for @discordjs/core/http-only

@discordjs/core/http-only

@discordjs/core/http-only

isn't giving any type declarations for some reason. easy workaround is to just import the types manually and use them when needed (as shown in the code snippet), but i just wanted to check if this was a known issue

d.js toolkit•10/28/23, 12:03 AM

What's your exact discord.js

npm list discord.js

npm list discord.js

and node

node -v

node -v

version?

Not a discord.js issue? Check out #other-js-ts.
Consider reading #how-to-get-help to improve your question!
Explain what exactly your issue is.
Post the full error stack trace, not just the top part!
Show your code!
Issue solved? Press the button!
```
✅
```
```
✅
```
Marked as resolved by staff

mikaelaOP•10/28/23, 12:05 AM

package version: 1.0.1
node version: 19.3.0

mikaelaOP•10/28/23, 12:08 AM

doesn't look like typescript can find any package at all, code works fine though

duck•10/28/23, 12:10 AM

code works fine though

if there are no issues when compiling, it sounds more like an ide issue
consider restarting your ts server

mikaelaOP•10/28/23, 12:11 AM

nope, same error after restarting ts server

mikaelaOP•10/28/23, 12:14 AM

don't know much about in package.json files but maybe thats the issue? importing the package normally works fine because of

main

main

, , and at the top, but nothing in is working

mikaelaOP•10/28/23, 12:16 AM

i can always add a ts-ignore to get rid of the type error and just import them manually, but it's not ideal

duck•10/28/23, 12:16 AM

again, if there are no issues when compiling, it sounds more like an ide issue
restarting your ts server was just a suggestion that could solve it

mikaelaOP•10/28/23, 12:16 AM

well yes, but it could be an issue with the package. i doubt it's a vscode issue anyway

mikaelaOP•10/28/23, 12:18 AM

works fine compiling (via nextjs) without the types too

mikaelaOP•10/28/23, 12:19 AM

should i make an issue on github?

Mmikaela works fine compiling (via nextjs) without the types too

duck•10/28/23, 12:19 AM

then I'm especially inclined to believe the issue is something local, even if it's not your ide

mikaelaOP•10/28/23, 12:20 AM

it might be, i just don't think there's anything else that could be effecting it.

mikaelaOP•10/28/23, 12:20 AM

i think i saw something like this happening when i was searching if it was a known issue, let me find it again

mikaelaOP•10/28/23, 12:22 AM

@duck found it

mikaelaOP•10/28/23, 12:22 AM

it can't be local

duck•10/28/23, 12:23 AM

I don't see why that means it can't be local

mikaelaOP•10/28/23, 12:23 AM

if it's happening on 2 different devices, possibly on 2 different ide versions too, i doubt it

mikaelaOP•10/28/23, 12:23 AM

they do seem to be using NextAuth though, i'm in a nextjs project too, so it may be that

mikaelaOP•10/28/23, 12:23 AM

but again, doubt

mikaelaOP•10/28/23, 12:24 AM

https://github.com/discordjs/discord.js/issues/9695#issuecomment-1629680669

mikaelaOP•10/28/23, 12:24 AM

found another

mikaelaOP•10/28/23, 12:24 AM

same error

mikaelaOP•10/28/23, 12:25 AM

and here

mikaelaOP•10/28/23, 12:25 AM

should i make an issue now?

duck•10/28/23, 12:28 AM

well then to address your question about the field more directly, the field has supported this style of pathing since node 12.16.0
I'm still not sure why you feel this is an issue with the package when your ide is the only thing reporting an issue, typescript has no issues compiling, and there are no issues actually running the code
if you really want to make an issue on github, you can, but I'm just telling you the issue is more likely to be local

mikaelaOP•10/28/23, 12:29 AM

i wasn't saying it was any issues with the code, i was just wondering if there could have been a mixup with importing the types

mikaelaOP•10/28/23, 12:29 AM

that's what my question was about

mikaelaOP•10/28/23, 12:30 AM

and it appears to be a pretty common issue given theres less than 5k npm downloads a month

mikaelaOP•10/28/23, 12:30 AM

most of which won't be using http-only

Mmikaela https://github.com/discordjs/discord.js/issues/9695#issuecomment-1629680669

mikaelaOP•10/28/23, 12:32 AM

i'll try messing around with my tsconfig since that's what they went on to do in this