feat: yarn migration

[Xetera]

Do we really need all of these files? Yarn 2 is such a hassle honestly I don't know of a single person who uses it

[SagnikPradhan]

Do we really need all of these files?

Assuming you are referencing to the sdk files, yes. It is for adding support to the editors.

Yarn 2 is such a hassle honestly I don't know of a single person who uses it

Do agree with it being hassle, but yarn is on version 3 now, classic isn't being updated.

[Xetera]

FYI you can use netlify dev to check to see if this builds locally instead of pushing potential fixes

[SagnikPradhan]

FYI you can use netlify dev to check to see if this builds locally instead of pushing potential fixes

OML sorry and thanks

[SagnikPradhan]

I think I am done with this, all there is left to do is probably the site configuration itself on dashboard.

[Xetera]

Sorry I don't really know what the issue with discord.js not being found is. Dev dependencies aren't being installed maybe?

[SagnikPradhan]

The scripts are being called using npm, they should be called with yarn.

[Xetera]

Can you add a netlify.toml to run that build step instead

[SagnikPradhan]

Sure, give me a few minutes.

[SagnikPradhan]

Geee, thanks.

[veksen]

I'm okay with the content of this PR, but this could/should have been split into smaller PRs, there's no good reason to bump the deps alongside moving to Yarn. If the PR was problematic, the whole thing would of been rolled back, undesirable :)

[SagnikPradhan]

If the PR was problematic, the whole thing would of been rolled back, undesirable :)

Sheesh, did not think about that.