Rikki Schulte
Rikki Schulte
Hmm, the typescript version must be resolving differently, either way you can use the ts-expect-error comment if you want since they are mostly just handling exceptions
This was the blocker we had run into before with pnpm, thus why i raised the issue of webpack support early on! Our plan was to migrate to vite instead,...
With vite the goal was to get rid of the duplicate typescript project references tree and use vite to bundle each library for it‘s relevant exports, but I’m having trouble...
Like I mentioned in #2185, you will need to find a compatibility mode or workaround for webpack 4, jest, cypress, etc, which has been what kept us from switching to...
@rxliuli that plugin looks very promising thanks! Apologies there seems to be a delay with my LTE connection, each of your comments is only visible once I make a comment?...
I think we can do this best in two or more PRs: 1. swap out webpack for vite - we don’t need to worry about bundling every library yet. Leave...
@leoloso yes that will come in a later version for 2. see the graphiql explorer example if you want to enable the explorer plugin Update: "later" as in later that...
@LekoArts this is looking great, thank you! also, hello and nice to see you again, welcome! i think all you need to do is to use `@graphiql/react` to [generate the...
can you show an example query that fails?
Unfortunately this might not be possible because we can’t import individual monaco.languages that we need like json. This isn’t as simple as changing the worker imports as you suggest, which...