James Viall

Hey all, what are the recommendations for configuring `graphql-codegen` to handle `@client` directives and cache-only fields?

I'd like this feature for a similar reason as @fbartho mentions. In notifications from Danger (PR comments / Emails), the red symbol gives a false signal. I'd love to be...

> I prefer .eslintrc as a format, and will stay with it until I’m absolutely forced not to. I’m happy to keep this PR open, though, to help eslint test....

I know it's been some time since this was opened, but it still is an issue even in version `2.0.0`. When trying to init Fullstory in a SSR React App,...

Related issue in Next.js issue: https://github.com/vercel/next.js/issues/58754

Just wanted to bump that I'm also hitting this still despite the fix--but probably because the main repo isn't using the latest wrapper? I did [submit a PR](https://github.com/codecov/codecov-action/pull/1864) to update...

> [@nmoinvaz](https://github.com/nmoinvaz) oh you mentioned `main` is also failing, can you shoot over a PR you see it on if possible? It's because `main` is still referencing [an old version...

I too am experiencing this, but I'm not using expo--using a proprietary react-native framework, so unable to provide a repro. Is there a clue to what this error actually means?...

> [@shellscape](https://github.com/shellscape) I think setting customLogger would work. https://vitejs.dev/config/shared-options.html#customlogger:~:text=Use%20a%20custom%20logger%20to%20log%20messages.%20You%20can%20use%20Vite%27s%20createLogger%20API%20to%20get%20the%20default%20logger%20and%20customize%20it%20to%2C%20for%20example%2C%20change%20the%20message%20or%20filter%20out%20certain%20warnings I'm trying to supress the same Sourcemap warning which keeps showing in my `vitest` runs, but my project does not directly...

Same same!