Arthur Lewis

Same issue here. Tried reverting to 0.21 as suggested in #338 but that made no difference for me.

Oh sorry, I should have said "suggested _by_ #338" - specifically @fcoury's mention that reverting to 0.21 worked fine. I'm seeing the issue on both 0.23 and 0.21.

@fcoury Yeah, I started at 0.23, but I get the same results if I delete the app and the symlink as you suggested before reinstalling, both with the ARM version...

To be clear, the app works fine, and the CLI tool works fine when the app is already open. It’s only when I use the command line to open the...

Having the same issue. Here's a minimal repo that gives me dozens of these warnings when I run `yarn build`. https://github.com/arthurthefourth/pseudo-class-test. I'm no Webpack expert, so it's possible I've got...

If it's helpful, I believe what's happening here is that `postcss-preset-env` is just unable to polyfill certain types of complex selectors with certain pseudo-classes, which GraphiQL's CSS uses. By default,...

I think this is an issue with the Chrome stable desktop release channel being different from the Chrome for Testing stable release channel. The [Chrome Releases blog](https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html) shows `121.0.6167.139` released...

I wonder what’s up with that `jq: command not found` you’re seeing. I saw it mentioned in another issue as well.

Ah right, I thought you'd linked to `install-chrome.sh`, not `install-chromedriver.sh`. I think there are a few separate issues which are getting conflated here: 1. As I mentioned above, `install-chrome.sh` seems...

@neospeed83 Do you think using the Chrome for Testing binaries for Chrome instead of the official releases isn't an option? That'd certainly be my preference, since those are already matched....