Vytenis

Also there is more getters not working - [ ] handbrakeActive - [x] lockState - [x] engineOn - [ ] getDoorState

There are two possible cases when it happens. > 1. If Vite or a plugin does not handle HMR, a full reload will happen. > 1. Also if there is...

The same is in my case. I have not released the package and just simply symlinked it in test project. By providing `--no-registry` flag I hope that peerDependencies will be...

Crinsane commented on Oct 11, 2015 so when?

What is source? Request ``` POST http://localhost:8080/v1alpha1/pg_dump HTTP/1.1 Content-Type: application/json X-Hasura-Role: admin { "opts": ["-O", "-x", "--schema", "public"], "clean_output": true, "source": "postgres" } ``` Response: ``` HTTP/1.1 400 Bad Request...

And what about `nextjs` Link element? The syntax looks like this ``` import Link from 'next/link'; .... Go home ```

> If it has a URL to navigate to, it should be an `a`, which in next.js and react-router means a `Link`. A `button` should only be for non-navigation behavior....

This is actually super cool idea. Store `report.json` as a cache key from base commit hash and use https://github.com/actions/cache#skipping-steps-based-on-cache-hit to skip tests if report is available :) please do not...

Demo repo https://github.com/FDiskas/parcel-bug

Related https://github.com/micromatch/picomatch/issues/64