Package upgrades and build issue fixes

[mtmacdonald]

Upgrades packages and attempts to work through build-related issues.

Resolved 🟢

• Upgrade all NPM packages to latest versions
• Regenerate yarn.lock from scratch (rm yarn.lock && yarn install) since some old versions of dependencies were still being pulled in
• Reverse the workaround minify: false from PR188. There is a better fix for #187. The oxc team answered in MR7855. The resolution was upgrading to vite 8.0.0-beta.8 including by regeneration of yarn.lock, followed by working through other issues related to plugin configs
• Improved vite-plugin-node-polyfills configuration (I got further on two issues, but removed package due to others, see below)
  • Removed the manual resolve configs, prompted by this reply
  • No longer blocked by #143 💪 (can't access lexical declaration '__buffer_polyfill' before initialization)

Remaining issues with vite-plugin-node-polyfills 🟠

• Production build (yarn build:docs) is back to showing Buffer is not defined at runtime 😞 No point using the plugin for now if we can only get it working in development builds.

• I also still get build warnings related to vite-plugin-node-polyfills. I think we could live with them short-term until the Vite 8 rollout and community packages are more finalised.

• #142

  • warning: esbuild option was specified by "vite-plugin-node-polyfills" plugin. This option is deprecated, please use oxc instead
  • Both esbuild and oxc options were set. oxc options will be used and esbuild options will be ignored

• We also have a dependabot warning #38 to resolve, that's pulled in by vite-plugin-node-polyfills. Looks like there is no fix yet - all known versions of elliptic package have this. Follow #344 and #144.

Conclusion

All packages are upgraded to latest versions, but I'm removing vite-plugin-node-polyfills until upstream issues are resolved. We can live with the Buffer is not defined runtime console warning from react-pdf - the app still functions.