Clint Pearson

This randomly started for me a few weeks back, I hadn't upgraded any of the chakra packages, but have just done so and made sure to update typescript and it's...

@donovanglover I'm unclear, however I've noticed the same behaviour happens with the full text search, which seems to behave very oddly under `--serve`. My (guess) is that there's something that...

Similarly the context isn't always there when the component mounts either, particularly if the component is being navigated to. It's unclear what's going on, but there seems to be a...

So it appears the context is only correct when the component mounts / unmounts as a direct result of a HARD browser refresh / entering the URL directly in the...

After a little bit of experimentation I think this might be a case of scope behaviour being a little unintuitive. When setting the `initiallyActiveScopes` to `{["none"]}` I can see that...

We're not using tailwind on our project (instead using Chakra) and this feels like a bad default to have out of the box given it's intended to be integrated into...

#10 also covers this and was IMO closed prematurely.

If I set my worker pool to only have a single worker (essentially emulating sequential processing) then the issue does disappear.

Just got caught out by this. The type supporting the `disabled` prop as well as `isDisabled` is a little confusing. Might be a good idea to signpost this in the...