Jacques Germishuys

> Maybe a workaround right now is to generate types for non-client preset use cases? e.g. > > ```ts > import type { CodegenConfig } from '@graphql-codegen/cli' > > const...

> Hi @jacquesg, > > You are right, you'd need to update your code to use the new generated file for your other use cases. > > Client preset doesn't...

The workaround is simply not workable. I would need to manually update around 80 files, which is really not okay for a minor version bump.

Put differently, the responsible action here is like I suggested, to revert the change and bump the version in accordance with the semver spec. If you don't do that, people,...

@eddeee888 Thank you for your effort to try and make this more palatable for people, but the issue remains that it is still a breaking change, and the defaults are...

> I think I need some help understanding "... going to impact users who don't use these internal types". Before 4.4.0 these internal types was generated regardless? How can these...

> [@palfaro91](https://github.com/palfaro91) unfortunately the only way at the moment is to use dynamic imports. That kinda works, but it doesn't work once you're using `jest`

Also happy to submit a PR to support both ESM and CommonJS.

Having started using the typedSql feature recently after having to resort to hand-written queries, I can say that this is an awesome feature! However, the burden of needing a real...

You can try something like the following. I've adjusted the padding of the editor to 24px, and use a 14px font. ```scss .code-line { position: relative; } .code-line::before { position:...