Luke Harries
Luke Harries
For reference, the way I managed to trigger the problem was as follows: ``` const MyComponent = (): JSX.Element => { const [count, setCount] = useState(0) useEffect(() => { posthog.capture('send...
Good question - I think we should define a timeout from the user side as this gives us maximum flexibility for the solution So explicitly: a timeout is when a...
On a side note: A quick win I've seen is if a user sees "There was an error completing this query" we should likely guide them on how to reduce...
@macobo how are we doing with deciding on this OKR? Would be great to get this finalized by EOD tomorrow (Thursday) if feasible
Discussed sync and the conclusion: "Aligned that timeouts are very important and a cause of frustration - but we don't need to have this at an OKR level as will...
@macobo up to you if you want to keep this issue open or close it
Hi @whollacsek, that should be fixed here: https://github.com/PostHog/posthog-js/pull/566 Would you mind updating to 1.50.7?
@cahyosubroto can you take this on?
We now offer a React provider, useful hooks and a comprehensive guide on how to use PostHog with client side and server side react: https://posthog.com/docs/integrate/third-party/next-js
We now our Next.js guide now talks about how to use server side feature flags: https://posthog.com/docs/integrate/third-party/next-js