feat(nuxt): Instrument storage API

[logaretm]

What

This PR adds automatic instrumentation for Nuxt's storage layer (powered by unstorage), enabling performance monitoring for cache and key-value storage operations in Nuxt/Nitro applications.

Storage operations will now automatically create performance spans with detailed attributes for observability in Sentry.

What's New

• Automatic Storage Instrumentation: Instruments all storage drivers configured in nuxt.config.ts via nitro.storage
• Comprehensive Coverage: Tracks all storage operations including:
  • getItem, setItem, hasItem, removeItem
  • Raw variants: getItemRaw, setItemRaw
  • Batch operations: getItems, setItems
  • Utility methods: getKeys, clear
  • Aliases: get, set, has, del, remove

Implementation Details

Span Attributes:

• sentry.op: cache.{operation} (e.g., cache.get_item, cache.set_item)
• sentry.origin: auto.cache.nuxt
• cache.key: Full key including mount prefix
• cache.hit: true for successful get/has operations
• nuxt.storage.op: Original method name
• nuxt.storage.mount: Storage mount point
• nuxt.storage.driver: Driver name (e.g., memory, fs, redis)

Files Changed:

• packages/nuxt/src/runtime/plugins/storage.server.ts - Runtime instrumentation plugin
• packages/nuxt/src/vite/storageConfig.ts - Build-time configuration
• packages/nuxt/src/module.ts - Module integration
• E2E tests for Nuxt 3 & 4

[linear]

JS-1016 [Nuxt/Nitro] Instrument KV Storage (instrumenting `unstorage`)

[cursor]

Bug: Incorrect Plugin Path in Storage Configuration

The addServerPlugin call in storageConfig.ts uses an incorrect relative path to the storage server plugin. Since storageConfig.ts is located in the vite directory, ./runtime/plugins/storage.server resolves to the wrong location, preventing the plugin from being found.

 

[logaretm]

Not a problem, the path isn't relative to current file, but to the module itself.