Sam Garson

+1, Amazon's approach seems the most logical, this could at least be given as an option in some config.

I've been receiving this as well, but only when the Edge runtime is enabled in Next. The fact that this works in the Nodejs runtime (for me), and that other...

Yeah, not sure what to say I'm afraid this is an odd one! It does feel like the dev app should have the react versions upgraded but not sure why...

I would also love to get some clarification on this—I assumed that safeReference would work in this case. Our use case is that we have a network of resources with...

We wrestled with this for a bit and ended up writing a custom resolver (using `get`/`set`) which allows us to set whether a reference is "required" or not (and therefore...

Hey @zcmgyu, for sure. It ended up being quite complex but it worked well for us. I've added the relevant code and specs here https://gist.github.com/samtgarson/f1a84096aa53786e9281bd36d4e2dc0a Worth noting that due to...

Just tried setting up a similar thing on a _separate_ Next.js, this time using Sentry, and effectively copy and pasted your example Sentry middleware, and I'm getting the same issue...

(Update: importing `@sentry/nextjs` instead of `@sentry/node` seems to have solved that, but this will not always be a viable workaround for other libraries)

Hey @jpwilliams thanks for the reply. I missed that middleware can hook into sending. It didn't occur to me to make a second client, this seems to have worked (with...

hey team, any news on this one? I've had to downgrade to 3.4 to avoid some other issues with 3.5, which isn't ideal. It would seem that this might not...