Matchu
4120c7aa88
Looks like there was some kind of runtime conflict when running @emotion/css and @emotion/react at the same time in this app? Some styles would just get clobbered, making things look all weird. Here, I've removed our @emotion/css dependency, and use the `<ClassNames>` utility element from `@emotion/react` instead. I'm not thrilled about the solution, but it seems okay for now... ...one other thing I tried was passing a `css` prop to Chakra elements, which seemed to work, but to clobber the element's own Emotion-based styles. I assumed that the Babel macro wouldn't help us, and wouldn't convert css props to className props for non-HTML elements... but I suppose I'm not sure! Anyway, I don't love this syntax... but I'm happy for the site to be working again. I wonder if we can find something better. |
||
|---|---|---|
| .. | ||
| HangerSpinner.js | ||
| ItemCard.js | ||
| OutfitMovieLayer.js | ||
| OutfitPreview.js | ||
| SpeciesColorPicker.js | ||
| useCurrentUser.js | ||
| useOutfitAppearance.js | ||
| WIPCallout.js | ||