Gabin Aureche

The fix proposed to this issue in #561 is part of my fork which is also published to npm, with automatic updates enabled: - Forked repository: [zhouzi/graphql-schema](https://github.com/zhouzi/graphql-schema) - npm package:...

From my understanding, this issue comes from the fact that react-intl is publishing non-transpiled file. The suggested solution is to tweak the webpack config, which is not possible without ejecting...

@christiankaindl any idea why the tests are failing? Is it a false positive or should the tests be updated? It'd probably be easier to get it merged if all checks...

This is a similar issue as #7634 `useSearchParams` reads from the `LocationContext`, `NavigationContext` and `RouteContext` (through `useNavigate`). So when a change is made to any of these, `useSearchParams` is updated...

The workaround for us is to set `debug` to `true` in development. This way we can find out errors that are thrown instead of returned. https://codesandbox.io/s/example-graphl-shield-throw-mfgle?file=/index.js

Thanks for reporting @Braunson 👍 This one should be easy to fix as we can safely escape curly braces there. I just created #17 to look into it.

Docusaurus pushed an update so Markdown files are not interpreted by MDX which solves this issue and others: https://github.com/facebook/docusaurus/issues/3018#issuecomment-1568123122

No problem, you're not bothering me at all, I'm always glad to get in touch with people using TheaterJS ;) Back then, when I first added `.stop()`, I wanted it...

I finally had some time, so here is the "[minimalist version](https://jsfiddle.net/p1e9La6w/)". I've also added a note in the documentation. I'd be curious to know if it actually fits your needs?

Glad you like it, that's actually the whole purpose of TheaterJS :)