Tech stack revamp

[solderq35]

Not high priority but could speed up / improve development improvement. Also applies to other VueJS projects in this organization.

• Move from Vue CLI to Vite (faster compilation with npm run dev, build
  • https://vueschool.io/articles/vuejs-tutorials/how-to-migrate-from-vue-cli-to-vite/
• Or, just upgrade Vue CLI if possible. Version 5.06 for instance supports NodeJS 18: https://github.com/vuejs/vue-cli/issues/7116#issuecomment-1161496270
  • So don't have to do openssl-legacy-provider anymore (tho I don't think it is security issue as we only use that argument in local dev): https://github.com/OSU-Sustainability-Office/energy-dashboard/blob/master/package.json#L6
• Vue2 to Vue3
  • Vue2 will stop receiving security updates and bug fixes December 31st, 2023
  • Probably not a huge security issue but yeah
  • https://v3-migration.vuejs.org/
  • Many breaking changes from Vue2 to Vue3, need to change many things in codebase, may or may not be worth

[solderq35]

Might be an issue in the future although for now seems like a warning that can be ignored; this is a dependency of vue-cli. Migrating to vite may be best option going forwards

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@achrinza/node-ipc@9.2.2',
npm WARN EBADENGINE   required: { node: '8 || 10 || 12 || 14 || 16 || 17' },
npm WARN EBADENGINE   current: { node: 'v18.18.2', npm: '9.8.1' }
npm WARN EBADENGINE }

up to date, audited 1805 packages in 11s

108 packages are looking for funding
  run `npm fund` for details

115 vulnerabilities (1 low, 71 moderate, 30 high, 13 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

[solderq35]

Double check that Vite replaces everything Babel used to do / check if anyone in the office uses Internet Explorer or older browsers