Antoine Niek

Seems like a lot of PRs/issues are trying to fix the same problem. This was for example my proposal to use the webpack logger API https://github.com/MatthieuLemoine/unused-webpack-plugin/pull/34

For other PRs trying to fix that issue also look at https://github.com/MatthieuLemoine/unused-webpack-plugin/pull/36 and https://github.com/MatthieuLemoine/unused-webpack-plugin/pull/35. Their approach is to output to a file instead of stdout.

Why even have a `useLazyQuery` if `useQuery` combined with `skip` and `refetch` already does the job (if indeed it's intended skip is ignored in refetch calls) ? Maybe useLazyQuery could...

For what it's worth we are experiencing similar issues with `navigator.cookieDeprecationLabel`, on some device `getValue` ~returns a promise that never resolves~, and others `navigator.cookieDeprecationLabel` is undefined or resolves to empty...

@bjoberg I forgot I was using a console logging filter and was inspecting the promise result using console.log. The absence of log output lead me to think the `then` handler...

Thanks @johnivdel and @jkarlin I'm not very familiar with how the experiments are pushed on browser instances. Is it tied to chrome profile / user identity? For this particular browser...