Error when building assets of panel
Yesterday when I tried installing a addon it gave me an error every time the building part was started by the installation process.
Solution:Jump to solution
1. Remove certain files and directories with
rm -r resources public node_modules.
2. Go through the Pterodactyl update documentation.
3. Install dependencies by running the yarn command.
4. Repair Blueprint with blueprint -upgrade.
5. Get some Blueprint extensions (if you haven't already) and install them onto your panel.Sent by prplwtf • byte snippet-upgrade
34 Replies
Heres the error
I know it's not related to blueprint but i can't use any addons or blueprint due to this error
Whats the error?
https://ptero.co/uvasutomas.typescript
RpcRemoteError: Plugin "react" was conflicted between ".eslintrc.js" and "../../../.eslintrc.js".
Sorry for ping forgot to disable
I'd suggest contacting the addon developer about this
Well the addon is working fine
Building panel frontend gives error
and if you remove the addon does it go away?
Nope
also why are you building the panel?
is the addon not compatible with blueprint?
The front end needs to be rebuilt every time a new addon is installed
It is compatible with blueprint
you don't need to build it
blueprint does that for you
Yes i don't
And that is failing
Blueprint building is getting an error
it is most deffo one of your addons causing that error then
No I've tested it in a different vps it's working just fine
if you do
blueprint -upgrade it'll basically reinstall blueprint and reset it to factory settingsSure I'll try that
and then you can easily reinstall the addons after that works
Even ptero rebuilding front end doesn't work
So maybe I messed up something globally
like using from the ptero docs?
Yes
that's normal
It gives the same error
oh
nvm
It gives the exact error
What's interesting is its to do with eslint, which is basically code formatting stuff
and react, which is what the frontend of pterodactyl is built on is confused on which one to use, even though there should only be one
I tried to ask in ptero discord but no response
Maybe I should also ask to eslint support
@ADI ; ) try the following
Solution
1. Remove certain files and directories with
rm -r resources public node_modules.
2. Go through the Pterodactyl update documentation.
3. Install dependencies by running the yarn command.
4. Repair Blueprint with blueprint -upgrade.
5. Get some Blueprint extensions (if you haven't already) and install them onto your panel.Sent by prplwtf • byte snippet-upgrade
Okay I'll try it
I can't try it out now since I will have to put panel in maintenance mode
What's wrong with that?
takes like less than 3 minutes
Im using a non-blueprint theme Medusa so I have to remove it before I install blueprint
Yesterday I tried shifting to blueprint since I got some addons
But it gave me those errors so i just reverted to a backup
That will be your issue, blueprint and any blueprint addon is incompatible with non-blueprint themes or addons since they have a high likelihood of overriding things vital to blueprints function
Yes that's why I said I can't run this now
I have to remove the theme and a subdomain addon and then try upgrading blueprint
Oh my bad, I read non-blueprint theme and just assumed you were trying to use both 😅
No problem
Blueprint makes it easy for me to not break anything while installing extensions on my panel
That's the reason I am shifting
But it didn't work yesterday so I will try it tonight
Okay it is now working
Just followed the upgrade guide