Andrzej Kiełtyka

@dorzgi, we changed our imports. Instead of getting errors from ```typescript import { TimeoutError } from "@opensearch-project/opensearch/lib/errors"; ``` we use exported `errors` const ```typescript import { errors as ElasticsearchErrors }...

I just encountered this issue. In my use case, I have some code that is being automatically generated before building the app. Because of that, it's not being pushed to...

In my remix app, when I try to upgrade graphiql to v2 and use the explorer plugin, I get the following error/stack after clicking the button to open explorer: ```...

@wilhelmeek, thank you. For some unknown reason, I had `@graphiql/react` 1.0.0-next.2 in my package.json. Using the latest 0.x version fixed the crash for me too. No idea how it got...

My other issue was resolved by rewriting components to use `GraphiQLProvider` + `GraphiQLInterface` with `useEditorContext`. My mistake was trying to keep my own state management instead of relying on your...

@GustavoCaso any update on that? :)

This bug with parsing very long decimal numbers is making the package unusable for people who want to stick to the built-in number/bigint instead of using bignumber package. :/

I just encountered this issue. I use type-graphql with class-validator. [graphql-scalars GraphQLJSONObject sets null prototype for the object.](https://github.com/Urigo/graphql-scalars/blob/543942ea8cabcd3bf924d916710b57591db8d95f/src/scalars/json/utils.ts#L36) [class-validator isNotEmptyObject validator uses hasOwnProperty.](https://github.com/typestack/class-validator/blame/63fe9c532fb6f633ddbb90e8225c5af49750513a/src/decorator/object/IsNotEmptyObject.ts#L21) Because the prototype is null, the hasOwnProperty...