Dominik Opyd

In fact, I have the same problem so I confirm that there is something wrong with this package.

I also have this bug on production Vercel. ```js ERROR TypeError: globals.Headers is not a constructor at server.js:52993:11 at http_HTTP.module.exports.http_HTTP. [as get] (.nuxt/http.js:113:0) at http_HTTP.module.exports.http_HTTP. [as $get] (.nuxt/http.js:126:0) ```

@danielroe The last time I used Vercel and Nitro I was dealing with this issue by a workaround. I created an `image.js` script that generated and save a `.vercel_build_output/config/images.json` in...

Is there any way around it? It causes quite a lot of problems ...

Adapter merged in another PR: https://github.com/dappradar/nft-sales-adapters/pull/140. I close.

@admah I will give you context using the example of a real application that I have been working with on Cloudflare for several years. I have the frontend of a...

@penalosa this is a bit unclear to me. Could you please show an example or documentation link - something that would visualize your solution?

There is a problem with correct Pull Request references. Everything in commits and even this PR points to invalid data. Probably by migration. #### Example: nuxt: Experimental server component islands...

I tested now this example in two version syntax `Options API` and `Sugar` and I can confirm that bug exist in `Options API` where on `Sugar` everything works fine. Demo...

@Shramkoweb This is not an bug. This functionality was introduced in version `12.2.0`. You, on the other hand, using version `12.1.0`. - https://github.com/vercel/next.js/releases/tag/v12.2.0 I think it's worth closing this issue.