Headers library running unexpectedly within Wrangler context

[niconiahi]

context: I'm running a Remix application deployed to Cloudflare Pages, using official plugins and CLIs. No weird stuff

when using the Headers library like this

import SuperHeaders from "@mjackson/headers"

async function invalidateCache(urls: string[], env: Env) {
  const headers = new SuperHeaders()
  headers.contentType = "application/json"
  headers.set("Authorization", `Bearer ${env.AUTHORIZATION}`)
  headers.set("X-Auth-Email", env.X_AUTH_EMAIL)
  headers.set("X-Auth-Key", env.X_AUTH_KEY)
  return fetch(`https://api.cloudflare.com/client/v4/zones/${env.ZONE_ID}/purge_cache`, {
    headers,
    method: "POST",
    body: JSON.stringify({
      files: urls,
    }),
  })
    .then((response) => {
      return response.json()
    })
    .catch((error) => {
      console.error("error", error)
    })
}

when this runs locally with pnpm run dev (remix vite:dev), the invalidation gets executed correctly

when running this, either deployed with pnpm run deploy (wrangler pages deploy ./build/client) or running the preview locally with pnpm run start (wrangler pages dev ./build/client), the headers don't get applied correctly. How do I know this? I get a Response letting me know there was an error (code 9106) which says: "Missing X-Auth-Key, X-Auth-Email or Authorization headers"

when refactoring the code to disregard using the Headers library, it works

async function invalidateCache(urls: string[], env: Env) {
  return fetch(`https://api.cloudflare.com/client/v4/zones/${env.ZONE_ID}/purge_cache`, {
    headers: {
      "Authorization": `Bearer ${env.AUTHORIZATION}`,
      "X-Auth-Email": env.X_AUTH_EMAIL,
      "X-Auth-Key": env.X_AUTH_KEY,
      "Content-Type": "application/json",
    },
    method: "POST",
    body: JSON.stringify({
      files: urls,
    }),
  })
    .then((response) => {
      return response.json()
    })
    .catch((error) => {
      console.error("error", error)
    })
}

let me know if I could provide any further information

[mjackson]

Are you using Remix's installGlobals function in production? If so, stop. People have reported various issues using it with the headers library.

[niconiahi]

I'm not actually. I just checked all over my codebase for installGlobals and didn't find any match

[mjackson]

It won't be in your codebase. It will be in remix-serve.