I was trying to figure out why my Webpack bundle included the graphql package, since I didn't think I depended on it anywhere. After digging through my Webpack stats in their analyzer, I discovered the culprit was using logErrorMessages from @vue/apollo-util:

To Reproduce
Steps to reproduce the behavior:

1. Import logErrorMessages anywhere in your app: import { logErrorMessages } from '@vue/apollo-util'
2. Build your app.
3. Use webpack-bundle-analyzer or similar to see graphql.js adding ~175KB to your bundle size.

Expected behavior
The util package would not depend on graphql.js for printing error messages, and not bloat bundle sizes.

For now, I'm just using console.error.

Versions
vue: 2.6.11
@vue/apollo-composable: 4.0.0-alpha.6
@vue/apollo-util: 4.0.0-alpha.6