Vue 3 + Vite

[ben]

This is an exploratory PR that changes up some of the fundamental building blocks of the system, without actually changing any UI (hopefully).

• Upgrading to Vue 3 (this is the current version, and most resources are targeting it now)
• Switching from Webpack to Vite (much simpler configuration, and makes reloading much easier)
• Dropping the requirements for the dlopen and vueport Foundry plugins (instead we'll bundle all of our requirements into ironsworn.js and pull it all down in one go)

There's a lot to this, and it's going to shake up a lot of files. Here are the resources I'm referencing:

• The FoundryVTT Wiki article on Vite
• The Lancer system which uses Vite for the full build
• The Archmage system, which uses Vue and Vite for part of the build

TODO

• Update npm dependencies
  • Vue and Vite
  • Drop all the webpack libraries
  • Update scripts to use vite
    • The build will be broken until either this Vite PR lands or Dataforged drops the import assertions
• Update readme with how to use vite
• Vite configuration
  • Build generates ironsworn.js
  • Dev mode loads properly with HMR for Vue and proxying to Foundry
  • vite build output shakes away parts of data forged
• Rewrite VueApplication to render using Vue 3
  • Fix drag and drop
  • Make sure clicking on images opens the image browser
  • SF character move sheet
  • SF setting-truths sheet
  • Sector sheet
• Rewrite IronswornVueActorSheet and children
  • IS character sheet
  • SF character sheet
  • Foe sheet
  • Location sheet
  • Shared sheet
  • Site sheet
  • Starship sheet
• Rewrite IronswornVueItemSheet and children
  • Asset sheet
  • Bondset sheet
  • SF move sheet
  • Progress sheet
• Update components to work with Vue 3
  • Replace tabbed-panels with slot-based components
  • Replace quill-editor with tinymce-editor based on this and use core Foundry settings for it
    • Fix the image browser
• Write a Vue3 plugin to replace the stuff in patchvue.js
• Updating theming strategy
• Update CHANGELOG.md

[rsek]

from what i can tell, that vite PR is intended to drop with 3.0, which is currently in beta - not sure what the timeline is there. if we wanted to get in ahead of that, a babel plugin suggested as a workaround here: vitejs/vite#4934 (comment)

[rsek]

some food for thought: is worth moving to vue3 composition API as the standard? i like the <script setup lang="ts"> flavour, myself.

an incremental migration might be possible - just make it part of component refactors. i'm not 100% clear on which flavours of Composition API can mix with the Options API though. but given that <script> and <script setup> can live in the same file, it might be ok.