Hanziness
fix: opt in to `import.meta.*` properties
This is a very early PR to make this app compatible with changes we expect to release in Nuxt v5.
In Nuxt v3.7.0 we added support for import.meta.* (see original PR) and we've been gradually updating docs and moving across from the old process.* patterned variables.
As I'm sure you're aware, these variables are replaced at build-time and enable tree-shaking in bundled code.
This change affects runtime code (that is, that is processed by the Nuxt bundler, like vite or webpack) rather than code running in Node. So it really doesn't matter what the string is, but it makes more sense in an ESM-world to use import.meta rather than process.
Hey @danielroe! Thank you very much for submitting this and for bringing my attention to the changes! I'll take a look at them shortly. I was planning to do some refactoring eventually, I'll add these changes to the list :)
