Migrate to Bun

[No767]

Summary

There were many many factors included here. Namely:

• Faster development speeds
• Improved DX
• Standarization of toolchain

Deno was analyzed and deeply investigated, but ultimately did not contribute to the vision. The goal is to have better DX, such as improved speeds, etc. UV is being used to standarize the toolchain with Kanae, and thus a simliar move was made here with Bun. Deno cares about security, Bun cares about speed. What benefits would we get if we switched to Deno? Better security, and the cost of performance. Deno also wraps around NPM packages for compatbility, destroying the main vision and goal of improved development speeds.

Performance should not be affected, as we are building into an static app regardless. In addition, several other notable changes are made to help get development started:

• Navbar icons now use the v2 logo (svg)
• Implemented hero section of the index page
• SVG-based favicons are used instead of the old version

Types of changes

What types of changes does your code introduce to the UC Merced's ACM Chapter Website?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
• All workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud