near-operation-file-preset with fragment masking?

[osdiab]

Hi all, in our project we are using the client-preset with a Hasura GQL schema (read: very big) and our gql documents in TypeScript files. We are finding that when changes to the typescript files cause the giant generated codegen file to be recreated, this causes our editor/lint performance to tank (with typescript-eslint) and also causes the NextJS dev server to become very unstable and slow since it also ends up recompiling a lot of code.

I'm thinking that this impact could be reduced significantly with something like the near-operation-file-preset since only small amounts of code would get regenerated as changes occur, but I was wondering before I sink a ton of time into this, if anyone knows if the fragment masking approach works with that? Because our codebase already bought into that and moving away from it would be both a bummer and also a pain.

(I also tried to move to gql.tada as a way to get around causing typescript changes whenever we change files during development, but turns out for a big Hasura schema it just causes the TypeScript compiler to run out of memory. Sad but perhaps that will get better in the future)

Thanks!