Re-applied patch for new version of @emotion/cache

Summary: Current patch was created for the previous version and patch-package shows warning about that on each yarn install. This diff re-applies the patch for the new version by invoking `patch-package emotion/cache` as suggested in the warning.

Reviewed By: passy

Differential Revision: D28443089

fbshipit-source-id: 277f8cdb1fb675b19685d9e98cdfdae6878b9ebc
This commit is contained in:
Anton Nikolaev
2021-05-14 10:22:28 -07:00
committed by Facebook GitHub Bot
parent 366752f424
commit 0212da0ba5

View File

@@ -1,10 +1,10 @@
diff --git a/node_modules/@emotion/cache/dist/emotion-cache.cjs.dev.js b/node_modules/@emotion/cache/dist/emotion-cache.cjs.dev.js
index b25808a..043f626 100644
index 5aae7dd..0f3e4c9 100644
--- a/node_modules/@emotion/cache/dist/emotion-cache.cjs.dev.js
+++ b/node_modules/@emotion/cache/dist/emotion-cache.cjs.dev.js
@@ -136,7 +136,7 @@ var createUnsafeSelectorsAlarm = function createUnsafeSelectorsAlarm(cache) {
}
unsafePseudoClasses.forEach(function (unsafePseudoClass) {
- console.error("The pseudo class \"" + unsafePseudoClass + "\" is potentially unsafe when doing server-side rendering. Try changing it to \"" + unsafePseudoClass.split('-child')[0] + "-of-type\".");
+// we're not doing SSR and not interested in pedantic errors: console.error("The pseudo class \"" + unsafePseudoClass + "\" is potentially unsafe when doing server-side rendering. Try changing it to \"" + unsafePseudoClass.split('-child')[0] + "-of-type\".");