Unable to deploy project because server size is too big and won't deploy

I continuously get the same error and has not been fixed yet, it usually happens once or twice and fixes itself, but it doesn't for some reason.

          This issue has happened again, but instead of all the games being like this, it only happens for certain games, and the site is broken when used in the proxy. The issue doesn't allow me to re-open it because it requires the person or author to be a collaborator.

Originally posted by @UnderC0verGoose in #23 (comment)

Polaris is too large for deployment.
I am using Vercel and Surge.
Fix?

like how would i do it (pls help)
someone told me to like change the HTML file name, but wont some code have to read that file name?
what code do I have to change too.

ty please help

I can't navigate website since the top bar thing is gone.

When I try playing cod mobile or roblox it continuously gives me a half screen and I'm not sure if this is on uv's side or now.gg's.

change link.com/games to link.com/gs.
such for the other sites

(like pretty much any other site)

or check the github repo and scroll through the documentation to deploy that to vercel.
i think that's a much better option

Most of the now.gg games are broken and are giving me UI bugs when loaded or clicked.

Error: A Serverless Function has exceeded the unzipped maximum size of 250 MB. : https://vercel.link/serverless-function-size

that's the error message I get

Vercel deployment does not go smoothly, and after tinkering with root directories and some ssl, I cannot fix it. You can't deploy to render and the other options require a credit card. My school already has blocked polarislearning.org, so another solution for this would be to make alternate links on other platforms.

Is it even possible to make it deploy on Vercel, and if so, can you please help me with doing so. Maybe make a guide?

Thanks in advance.

To quote a stackoverflow user:

package-lock.json is automatically generated for any operations where npm
modifies either the node_modules tree, or package.json. It describes the
exact tree that was generated, such that subsequent installs are able to
generate identical trees, regardless of intermediate dependency updates.

This file is intended to be committed into source repositories, and serves
various purposes:

• Describe a single representation of a dependency tree such that teammates, deployments, and continuous integration are guaranteed to install exactly the same dependencies.

• Provide a facility for users to "time-travel" to previous states of node_modules without having to commit the directory itself.

• To facilitate greater visibility of tree changes through readable source control diffs.

• And optimize the installation process by allowing npm to skip repeated metadata resolutions for previously-installed packages.

One key detail about package-lock.json is that it cannot be published, and it
will be ignored if found in any place other than the toplevel package. It shares
a format with npm-shrinkwrap.json, which is essentially the same file, but
allows publication. This is not recommended unless deploying a CLI tool or
otherwise using the publication process for producing production packages.

If both package-lock.json and npm-shrinkwrap.json are present in the root of
a package, package-lock.json will be completely ignored.

Source: https://stackoverflow.com/a/44210813