Roman Schmid

Just encountered the same issue, since I wanted to update a class on an element via the `outrostart` event. eg. ```svelte import {fade} from "svelte/transition"; export let isOpen = false;...

Are you using SvelteKit by any chance? We ran into the same issue, but it's actually related to SvelteKit. Their `fetch` implementation strips response headers and thus generates the error,...

Ok, maybe your graphQL Server doesn't sent the proper `content-type` header? That would result in the same behavior.

I suggest you check if the response from your graphql-endpoint contains the proper `content-type` header… it should be `application/json`

I think this issue is also related to #373 @MeloHenrique maybe you could create a PR that relaxes https://github.com/prisma-labs/graphql-request/blob/master/src/index.ts#L667 to allow other content-types, such as `application/graphql+json`?

I can already specify a region when writing functions, like described here: https://firebase.google.com/docs/functions/locations#best_practices_for_changing_region Or are you referring to something else?

@junaga Ah I see, thanks for the heads-up

Not sure if this warrants a separate issue, but it seems that the path to `version.json` is not considering the `assets` path setting. Let's say `paths.assets` is `https://example.com/assets`, it would...

We seem to get this new simulated CORS error a lot on netlify deploys. Not sure if there's some caching going on or if the render-function sets the origin to...

The approach with the global wrapper didn't work for me either. Did the syntax for `addDecorator` change in any way? Works fine when using a decorator in the `*.stories.svelte` file,...