How do you deal with large packages checked in .yarn/cache with compressionLevel: 0?

[stovmascript]

I'm updating our .yarn/cache and would like to migrate to the default compressionLevel of 0 as it makes sense and truly reduces the size being transferred over the wire during checkout.

Some of our dependencies are quite large though and I'm already running into warnings and errors from GitHub's file size limits:

remote: warning: File .yarn/cache/highcharts-npm-10.3.3-c7af5563d7-c9bdc27046.zip is 77.40 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File .yarn/cache/next-npm-13.5.3-a023378618-aa1cd95d7f.zip is 55.39 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File .yarn/cache/typescript-npm-4.7.3-edc6629fdf-4f2597ac20.zip is 64.09 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File .yarn/cache/typescript-npm-4.9.5-6427b65ee6-5f6cad2e72.zip is 63.77 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File .yarn/cache/typescript-patch-32ada147aa-e3333f887c.zip is 63.85 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File .yarn/cache/typescript-patch-e954a37a86-fd3972aed0.zip is 64.16 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: error: Trace: eb8e6643088372f3c974d8c4a8abddc297ae29c9411a929e127abdc7415f187b
remote: error: See https://gh.io/lfs for more information.
remote: error: File .yarn/cache/@next-swc-darwin-arm64-npm-13.5.3-a78869bc98-10c0.zip is 102.69 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File .yarn/cache/@next-swc-darwin-x64-npm-13.5.3-3a4452c378-10c0.zip is 104.23 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.

I'm curious how would you approach this?

The files that result in error are native builds, which I'm thinking of ignoring from the cache altogether, as they should be fetched, prior to a build on the host machine, albeit breaking the offline mirror feature a bit.

Another possibility would be to track everything +50M with LFS, but as I understand there are some transfer limits and also it's currently not possible to track in LFS by file size. It also seems kind of weird to track files which are available on a public registry.