Update Dependencies for Security Issues

[CanerKaraca23]

This PR updates and refreshes all dependencies to latest versions.

Updating typescript dependency breaks built, a fix from developers will be welcomed and appreciated.

It fixes 11 "known" security issues. 6 high, 4 moderate, 1 low security issue and maybe even more...

• CVE-2023-42282
• CVE-2024-4068
• CVE-2024-27308
• CVE-2024-28849
• CVE-2024-29415
• CVE-2024-31207
• CVE-2024-35222
• CVE-2024-37890
• CVE-2024-39008

[AmyrAhmady]

It doesn't even build
If you manage to fix building issues I'll merge this
Otherwise I see absolutely no reason to update any dependency at all. none of those security issues are even remotely related to our usage

[CanerKaraca23]

It doesn't even build If you manage to fix building issues I'll merge this Otherwise I see absolutely no reason to update any dependency at all. none of those security issues are even remotely related to our usage

Downgraded typescript, it should be fine now for merge.

However, even i downgrade typescript and refresh yarn.lock, still fails so i only refreshed cargo. Couldn't manage to fix build issues unfortunately. I expected from developers for fixing.

CVE-2023-42282
CVE-2024-29415

security issues left because of yarn.lock refresh breaks build.

[AmyrAhmady]

I expected from developers for fixing.

CVE-2023-42282 CVE-2024-29415

security issues left because of yarn.lock refresh breaks build.

When you make a PR, it is expected to make it working. You can add breaking changes and expect it to be merged and make developer responsible to fix it

And regarding those security issues, if you read the details you realize neither of them is used in the project, so it doesn't affect us, just like all the other security issues

[CanerKaraca23]

I expected from developers for fixing.
CVE-2023-42282 CVE-2024-29415
security issues left because of yarn.lock refresh breaks build.

When you make a PR, it is expected to make it working. You can add breaking changes and expect it to be merged and make developer responsible to fix it

And regarding those security issues, if you read the details you realize neither of them is used in the project, so it doesn't affect us, just like all the other security issues

Thanks, build passes now.

Keeping dependencies up-to-date is always good i think, not only for security, bug fixes, improvements etc.