fix: opt in to import.meta.* properties

[danielroe]

Is your PR related to a specific issue/feature? Please describe and mention issues.

This is a very early PR to make this module 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.

(It might be worth updating the module compatibility as well to indicate it needs to have Nuxt v3.7.0+, but I'll leave that with you if you think this is a good approach.)

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Checklist:

• Code style and linters are passing
• Backwards compatibility is maintained
• Requires documentation to be updated

[manchenkoff]

Hey @danielroe, thanks for the contribution! That totally makes sense, I recently updated compatibility to nuxt: '^3.9.0', so it should be fine