Hung Viet Nguyen
Hung Viet Nguyen
How to see the cache key by yourself 1. Run `jest --clearCache` to see where the cache located. For e.g, on mac: `/private/var/folders/hg/cg39z3hd4gv3grbrd08524gh0000gp/T/jest_dy` 2. `cd` to that project and explore
My hypothesis: If we do not explicitly implement `getCacheKey`. It will use `src` and `filename` as cache key. So, we should add transformer file content into account. So each time...
Motivation for this issue: When reviewing code for #129
https://stackoverflow.com/questions/65242830/in-a-github-actions-workflow-is-there-a-way-to-have-multiple-jobs-reuse-the-sam
@all-contributors please add @ntbinh-Harvey for test
Hi @ParamagicDev. Thank you for reporting this issue to us. I haven't tried Jest Preview in WSL, also, we are having an issue on Linux that the Jest Preview Dashboard...
@ParamagicDev Can you please update `jest-preview` to the newest version (`>= 0.2.8`) then try again. We fix that issue in https://github.com/nvh95/jest-preview/pull/200. Thanks.
We tested the core function of `jest-preview` on - [x] Mac (development machine) - [x] Ubuntu - [x] Windows We also have CI to run on Ubuntu and Windows (GitHub...
Are we just re-implementing the default behavior of Jest's getCacheKey?
@LayZeeDK > I just read the raw global CSS stylesheet and append it to the document. I don't know how we would add Sass support although it is supported by...