32 Replies
hmmmm, show your code?
i havent edited it lol
i just updated my npm
cause of the djs update but
hmmmm, thats weird. @Favna ?
ever since it just spams this in the console
i saw another post here about the same thing, but his node was outdated
mine isnt
which node version you using?
v18.17.0
hmmm, im on 18.50.0 but i cant see that making a huge difference
we'll wait and see what Favna says
yeah ive no clue
i downgraded to ur version just to check if it was node that was the issue
and it aint
ripppp
the full error
i temp fixed it by removing reason.constructor but
idk how long this will last LOL
I had this issue when running my code in my vscode debugger, but not when running it directly.
I didn't troubleshoot it but I'll look into it next time if nobody resolves this first
@kyra 🩵🩷🤍🩷🩵
@dayflare eval or console.log
process.version
, please@kyra 🩵🩷🤍🩷🩵 v16.15.0
Sorry for the delay.
Yeah so you're not on v18
Still, that shouldn't have failed, it doesn't in CI
I updated to the latest node using nvm
I'm using PM2 to keep it alive.
Try start it without pm2 for a moment, just use
node
Get same error?Ah right, its now printing v18.
Alright I rebuilt NPM and updated PM2 and it seems to be working now.
Good stuff
Thanks for your help 🙂
Although I do have another question if you don't mind- although it is small.
Go ahead
@dayflare
My API Get Route isn't accepting any spaces in the Query Params and will throw 404 if there are any.
Although if it's just one word without a space it works fine.
Typically you shouldn't have a space in a URL
What's the use-case here?
In the front-end
Try and do it like
/role%20name
Cause yeah, URLs don't contain spaces, a space is represented by a %20
Which your code is already replacing the %20, so you must've already been somewhat aware of this
Yeah I knew that but it just generally wasn't sending, lemme try this rq.
A little side note, make sure your your primary server has a privacy policy / user consent for sharing their user ID's to a third party
Yeah, I think I've found the issue, probably best if I move over to Role ID's to be honest being some of my roles contain special characters which don't have URL support.
Cause if you type a URL with a space in a browser, it just Google's it too
Yeah, thanks for the help anyway been a big help haha 🙂
No problem
Also, you could always use a POST request and pass a role name to the body, that will parse your special characters