jest-glamor-react

version: 4.3.1 version: 9.11.2 (or ) version: 6.1.0 What you did: I have two repositories, one that contains a UI library using glamour and the other that contains our production site, also using glamor. Both are using the same version of jest-glamor-react. In our main repo, when we have the UI library installed normally, we see the styles come through on all components, and all is well. But when running npm link to symlink to a local copy of the UI library, components from that library no longer get transformed, and we just get data-css-hash in our snapshots for those components. Reproduction repository: https://github.com/chrissinclairedited/jest-glamor-react-issue-library https://github.com/chrissinclairedited/jest-glamor-react-issue-client Clone both and link client -> library (the dependency in client is expecting it to be called library) and the tests pass. But looking at the snapshots for the client, the test that depends on the library component doesn't include the styles. Problem description: Snapshots are not transforming css classes when the component exists in a locally linked repo. Suggested solution: Treat locally linked libraries the same way as locally installed ones and transform the styles on that repo.

We are using jest-glamor-react in production in our company and so far, this is a super piece of code. Thanks for your awesome work 👍! What: I've recently (first time ever) faced a weird issue in some of our (non open-sourced) components: The error is thrown only because of the snapshot creation. Removing the line fixes it (but this obviously not what we want). We are using Enzyme and all the other tests are passing (i.e. nothing is broken). The issue was triggered after splitting one component in smaller chunks. Why: For some reason, the are undefined in the method (utils). Consequently, an error is thrown in https://github.com/kentcdodds/jest-glamor-react/blob/master/src/utils.js#L37-L38 when trying to access the property of the object. How**: The changes involved are quite simple, returning an empty array early actually solves it. The unit tests of the repository are passing and our tests are not altered at all (a good sign!).

resolve #36 What: Support asymmetric matchers (#36) Why: Using asymmetric matchers make tests easier How**: see https://github.com/facebook/jest/blob/be4bec387d90ac8d6a7596be88bf8e4994bc3ed9/packages/expect/src/jasmine_utils.js#L36 This can support , and , but I do not know how to add exclusive-or-ly those peerDeps. Is there a way to do so?