What. The. Hell
So it seems like my whole pterodactyl panel is done for ? I just did a types.d.ts file to make vscode shut up about the missing elements for Typescript but now even with the file removed i get this MASSIVE wall of errors when doing a yarn build, do i need to go nuclear on this or there's a fix to avoid loosing anything ?
Solution:Jump to solution
So even after updating i still have a borked panel, will need to reinstall unfortunately
24 Replies
Did you use npm to install your packages?
No i just built after that types.d.ts file was created and vscode stopped whining
with blueprint -build
uh could you try removing your node_modules folder and running
yarn installi did, multiple times
huh..
okay give me a few minutes
👍
or maybe hours, not sure, gotta figure out what is still breaking in pterodactyl
yeah np take the time you need to figure it out
having the same issue right now. im completely lost
oh so its not a me issue, wellp it reasures me but also not really at the same time (it means i didnt broke smth, ahah)
im incredibly confused
yknow what- im giving up on the new colors thing
you think its related to that ? I mean, yeah must be since its the only recent change
i've been trying to get this to work properly for over a week now, and i've only made slight process, which breaks on half the devices its tested on
tailswing css v4 right ?
v3
we at what ver curently before that ?
no v4 is latest, ptero uses v3.0.24
so you tried to make v3 work right and it just doesnt, correct ?
cuz ive seen the v4 update
so i'm kinda confused now
oh i see whats going on probably
oh this is lovely
ok im going to very carefully redo the things i implemented earlier
Solution
So even after updating i still have a borked panel, will need to reinstall unfortunately
i found the issue, run
blueprint -upgrade remote firsti had did, until i wiped everything after archiving and downloading the whole panel files to put them back later
wich i now did and its running, until i really need to update BP i wont then