Cache update errors are caught

[bkiac]

I had an error in my update resolver logic which was really hard to find because the error was caught by the cache exchange like nothing happened. I'm not sure if this is intentional or not.

urql version & exchanges:

urql	2.0.6
@urql/exchange-graphcache	4.3.6

Steps to reproduce

const cache: GraphCacheConfig = cacheExchange({
	schema,
	updates: {
		Mutation: {
			doSomething: () => {
				throw new Error("this is caught")
			},
		},
	},
})

Expected behavior
Errors are propagated/re-thrown

Actual behavior
Errors are caught inside the cache exchange

[JoviDeCroock]

Nothing in urql is catching these we are throwing them for the user, here is a simple reproduction highlighting this case. When you press a todo it will throw an error.

EDIT: updating to 2.0.6 seems to introduce this issue 😅 this issue seems to be introduced in 2.0.5. This bug seems related to the changes we did in core at 2.3.0, the incremental delivery is eating the error and returning it as an error instead