How does Vite handle caching for OPTIONS requests?

[BenedictLang]

I have a caching config for an API GET request:

VitePWA({
      // https://vite-pwa-org.netlify.app/guide/
      registerType: 'autoUpdate',
      devOptions: {
        enabled: false
      },
      injectRegister: 'auto',
      workbox: {
        globPatterns: ['**/*.{js,css,html,ico,png,svg,woff2,glb,json}'], // Files matching any of these patterns will be included in the precache manifest.
        maximumFileSizeToCacheInBytes: 15000000, // 15 MiB
        runtimeCaching: [{
          urlPattern: ({url }): boolean =>
            url.href.startsWith('https://www.domain.com/api/'),
          method: 'GET',
          handler: 'NetworkFirst', // Prefer making API request. If not possible (e.g. no network connection), fall back to cache.
          options: {
            cacheName: 'api-cache',
            cacheableResponse: {
              statuses: [0, 200] // 0 = opaque responses, as defined in the Fetch API.
            },
            networkTimeoutSeconds: 10 // Keep the timeout this high! Otherwise, workbox might be unable to respond with the cached version fast enough.
          }
        }]
      },
      [...]
      

When moving to a live server, we get a fetch failure. Looking into the requests, the service worker seems to trigger the browser to make a preflight request. It sends a OPTIONS request.
Most caching strategies don't cache OPTIONS requests, especially in scenarios like CORS preflight checks, as they are preflight verifications and don't carry the data or response you'd typically cache.

Is that the case in VitePWA?