Merge branch 'next' into theming-in-v10

.changeset/README.md

@@ -0,0 +1,36 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with `bolt` to help you release components from a mono-repository. You can find the full documentation for it [here](https://www.npmjs.com/package/@changesets/cli)
+
+To help you get started though, here are some things you should know about this folder:
+
+## Changesets are automatically generated
+
+Changesets are generated by the `yarn changeset` or `npx changeset` command. As long as you are following a changeset release flow, you shouldn't have any problems.
+
+## Each changeset is its own folder
+
+We use hashes by default for these folder names to avoid collisions when generating them, but there's no harm that will come from renaming them.
+
+## Changesets are automatically removed
+
+When `changeset bump` or equivalent command is run, all the changeset folders are removed. This is so we only ever use a changeset once. This makes this a very bad place to store any other information.
+
+## Changesets come in two parts
+
+You should treat these parts quite differently:
+
+- `changes.md` is a file you should feel free to edit as much as you want. It will be prepended to your changelog when you next run your version command.
+- `changes.json` is a file that includes information about releases, what should be versioned by the version command. We strongly recommend against editing this directly, as you may make a new changeset that puts your bolt repository into an invalid state.
+
+## I want to edit the information in a `changes.json` - how do I do it safely?
+
+The best option is to make a new changeset using the changeset command, copy over the `changes.md`, then delete the old changeset.
+
+## Can I rename the folder for my changeset?
+
+Absolutely! We need unique hashes to make changesets play nicely with git, but changing your folder from our hash to your own name isn't going to cause any problems.
+
+## Can I manually delete changesets?
+
+You can, but you should be aware this will remove the intent to release communicated by the changeset, and should be done with caution.

.changeset/config.json

@@ -0,0 +1,30 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    { "repo": "emotion-js/emotion" }
+  ],
+  "commit": false,
+  "linked": [
+    [
+      "@emotion/core",
+      "@emotion/styled",
+      "@emotion/styled-base",
+      "@emotion/cache",
+      "@emotion/css",
+      "create-emotion",
+      "emotion",
+      "emotion-server",
+      "create-emotion-server",
+      "babel-plugin-emotion",
+      "@emotion/babel-preset-css-prop",
+      "jest-emotion",
+      "@emotion/native",
+      "@emotion/primitives",
+      "@emotion/primitives-core",
+      "eslint-plugin-emotion",
+      "emotion-theming"
+    ]
+  ],
+  "access": "public"
+}

.changeset/curvy-timers-decide.md

@@ -0,0 +1,5 @@
+---
+'@emotion/styled': major
+---
+
+Remove support for deprecated `innerRef` prop

.changeset/five-spoons-roll.md

@@ -0,0 +1,5 @@
+---
+'@emotion/serialize': patch
+---
+
+Throw error about invalid content property values instead of just logging error to the console.

.changeset/flat-adults-add.md

@@ -0,0 +1,5 @@
+---
+'jest-emotion': patch
+---
+
+Take specificity into account when matching styles

.changeset/giant-oranges-impress.md

@@ -0,0 +1,6 @@
+---
+'babel-plugin-emotion': major
+'@emotion/babel-preset-css-prop': major
+---
+
+Removed support for the `instances` option, any usage of it should be replaced with the `importMap` option

.changeset/light-mice-relate.md

@@ -0,0 +1,5 @@
+---
+'babel-plugin-emotion': patch
+---
+
+Avoid transpiling vanilla emotion calls in already transpiled code to avoid double labels and such

.changeset/long-apes-admire/changes.json

@@ -0,0 +1,31 @@
+{
+  "releases": [
+    { "name": "@emotion/css", "type": "major" },
+    { "name": "emotion-theming", "type": "major" },
+    { "name": "@emotion/serialize", "type": "major" },
+    { "name": "@emotion/styled-base", "type": "major" },
+    { "name": "@emotion/styled", "type": "major" }
+  ],
+  "dependents": [
+    {
+      "name": "babel-plugin-emotion",
+      "type": "patch",
+      "dependencies": ["@emotion/serialize"]
+    },
+    {
+      "name": "@emotion/core",
+      "type": "patch",
+      "dependencies": [
+        "@emotion/css",
+        "emotion-theming",
+        "@emotion/serialize",
+        "@emotion/styled"
+      ]
+    },
+    {
+      "name": "create-emotion",
+      "type": "patch",
+      "dependencies": ["@emotion/serialize"]
+    }
+  ]
+}

.changeset/long-apes-admire/changes.md

@@ -0,0 +1,31 @@
+TypeScript types have been restructured. These changes:
+
+- Reduce build times when using emotion
+- In many cases remove the need for manually specifying generic parameters for your emotion components.
+
+If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.
+
+## Improvements
+
+- useTheme added to EmotionTheming interface and can now create your own closed variation of withTheme. More information in the docs under the theming section.
+- Union types as props are better supported and should be inferred properly
+- Build times should be reduced significantly in larger projects.
+
+## Breaking changes
+
+- withTheme can now have the Theme type specified when calling it. For example `withTheme<MyTheme>(MyComponent)`
+
+  **Breaking change:** Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section
+
+- `css` function has been restricted to prevent passing of invalid types
+- `CreateStyled` functions no longer take a second `ExtraProps` argument. Instead move it to after the create styled call. For example
+
+  `styled<typeof MyComponent, ExtraProps>(MyComponent)({})`  
+  to  
+  `styled(MyComponent)<ExtraProps>({})`
+
+- `StyledComponent` type no longer supports the third generic `Theme` parameter. Instead add the `theme` prop to the first `Props` argument. For example:
+
+  `StyledComponent<Props, {}, MyTheme>`  
+  to  
+  `StyledComponent<Props & { theme?: MyTheme }>`

.changeset/mean-deers-confess.md

@@ -0,0 +1,5 @@
+---
+'jest-emotion': major
+---
+
+Added the `T` parameter to the `Matchers` interface in the TypeScript definitions to make this module compatible with `@types/jest@^24.0.20`.

.changeset/modern-grapes-obey.md

@@ -0,0 +1,5 @@
+---
+'babel-plugin-emotion': major
+---
+
+Drop Babel 6 support

.changeset/neat-ligers-film.md

@@ -0,0 +1,5 @@
+---
+'babel-plugin-emotion': patch
+---
+
+Fix issue with not updating referenced import when bailing out on already transpiled vanilla emotion nodes (a regression introduced in #1602)

.changeset/nine-mugs-care.md

@@ -0,0 +1,7 @@
+---
+'@emotion/core': patch
+'@emotion/is-prop-valid': patch
+'@emotion/serialize': patch
+---
+
+Add missing `#__PURE__` annotations

.changeset/pre.json

@@ -0,0 +1,58 @@
+{
+  "mode": "pre",
+  "tag": "next",
+  "initialVersions": {
+    "babel-plugin-emotion": "10.0.23",
+    "@emotion/babel-plugin-jsx-pragmatic": "0.1.4",
+    "@emotion/babel-preset-css-prop": "10.0.23",
+    "@emotion/cache": "10.0.19",
+    "@emotion/core": "10.0.22",
+    "create-emotion": "10.0.14",
+    "create-emotion-server": "10.0.14",
+    "@emotion/css": "10.0.22",
+    "emotion": "10.0.23",
+    "emotion-server": "10.0.17",
+    "emotion-theming": "10.0.19",
+    "eslint-plugin-emotion": "10.0.14",
+    "@emotion/hash": "0.7.3",
+    "@emotion/is-prop-valid": "0.8.5",
+    "jest-emotion": "10.0.17",
+    "@emotion/memoize": "0.7.3",
+    "@emotion/native": "10.0.22",
+    "@emotion/primitives": "10.0.24",
+    "@emotion/primitives-core": "10.0.22",
+    "@emotion/serialize": "0.11.14",
+    "@emotion/sheet": "0.9.3",
+    "@emotion/styled": "10.0.23",
+    "@emotion/styled-base": "10.0.24",
+    "@emotion/stylis": "0.8.4",
+    "@emotion/unitless": "0.7.4",
+    "@emotion/utils": "0.11.2",
+    "@emotion/weak-memoize": "0.2.4",
+    "example": "0.6.17",
+    "my-razzle-app": "0.1.3",
+    "babel-preset-emotion-dev": "9.2.6",
+    "babel-tester": "0.4.5",
+    "benchmarks": "0.8.27",
+    "old-babel-tester": "0.4.5",
+    "ssr-benchmarks": "0.8.13",
+    "test-utils": "0.3.2",
+    "emotion-site": "9.3.0"
+  },
+  "changesets": [
+    "long-apes-admire",
+    "curvy-timers-decide",
+    "five-spoons-roll",
+    "flat-adults-add",
+    "giant-oranges-impress",
+    "light-mice-relate",
+    "neat-ligers-film",
+    "nine-mugs-care",
+    "rare-books-own",
+    "rare-toes-grow",
+    "spotty-llamas-mate",
+    "strange-pumas-suffer",
+    "stupid-radios-draw",
+    "two-baboons-mate"
+  ]
+}

.changeset/rare-books-own.md

@@ -0,0 +1,18 @@
+---
+'babel-plugin-emotion': major
+'@emotion/cache': major
+'@emotion/core': major
+'create-emotion': major
+'create-emotion-server': major
+'@emotion/css': major
+'emotion': major
+'emotion-server': major
+'emotion-theming': major
+'jest-emotion': major
+'@emotion/native': major
+'@emotion/primitives': major
+'@emotion/primitives-core': major
+'@emotion/styled': major
+---
+
+Ensure packages are major bumped so that pre-release versions of the linked packages are consistent in the major number

.changeset/rare-toes-grow.md

@@ -0,0 +1,5 @@
+---
+'jest-emotion': patch
+---
+
+Match rules in declarations with component used as a selector

.changeset/spotty-llamas-mate.md

@@ -0,0 +1,7 @@
+---
+'babel-plugin-emotion': major
+'@emotion/styled-base': major
+'@emotion/styled': major
+---
+
+Removed support for `@emotion/styled-base` package. It has been moved to `@emotion/styled` and is available as `@emotion/styled/base`. This simplifies how the regular and base versions relate to each other and eliminates problems with stricter package managers when `@emotion/styled-base` was not installed explicitly by a user.

.changeset/strange-pumas-suffer.md

@@ -0,0 +1,5 @@
+---
+'@emotion/styled': patch
+---
+
+StyledComponent Flow type is now polymorphic, that means you can now define the component prop types to get better type safety.

.changeset/stupid-radios-draw.md

@@ -0,0 +1,6 @@
+---
+'babel-plugin-emotion': minor
+'@emotion/babel-preset-css-prop': minor
+---
+
+Added the `importMap` option which allows you to tell babel-plugin-emotion what imports it should look at to determine what it should transform so if you re-export Emotion's exports, you can still use the Babel transforms

.changeset/two-baboons-mate.md

@@ -0,0 +1,10 @@
+---
+'@emotion/core': major
+'emotion-theming': major
+'@emotion/native': major
+'@emotion/primitives-core': major
+'@emotion/primitives': major
+'@emotion/styled': major
+---
+
+Use hooks internally for improved bundle size and a better tree in React DevTools

.circleci/config.yml

@@ -2,17 +2,16 @@ version: 2
 jobs:
   flow:
     docker:
-      - image: circleci/node:10.6.0-browsers
+      - image: circleci/node:10.16.3-browsers
     working_directory: ~/repo
     steps:
       - checkout
       - restore_cache:
           keys:
-            - v2-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v2-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
-      - run: yarn flow start --file-watcher=none
       - run: yarn flow:check
       - run: yarn build
       - run: cd scripts/benchmarks && yarn build
@@ -22,19 +21,19 @@ jobs:
           paths:
             - ~/.cache/yarn
             - node_modules
-          key: v2-dependencies-{{ checksum "yarn.lock" }}
+          key: v4-dependencies-{{ checksum "yarn.lock" }}
 
   test:
     docker:
-      - image: circleci/node:10.6.0
+      - image: circleci/node:10.16.3
     working_directory: ~/repo
     steps:
       - checkout
       - restore_cache:
           keys:
-            - v2-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v2-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run:
           name: Jest Tests
@@ -49,15 +48,15 @@ jobs:
 
   test_dist:
     docker:
-      - image: circleci/node:10.6.0
+      - image: circleci/node:10.16.3
     working_directory: ~/repo
     steps:
       - checkout
       - restore_cache:
           keys:
-            - v2-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v2-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run:
           name: Jest Tests
@@ -67,15 +66,15 @@ jobs:
 
   lint_and_typescript:
     docker:
-      - image: circleci/node:10.6.0
+      - image: circleci/node:10.16.3
     working_directory: ~/repo
     steps:
       - checkout
       - restore_cache:
           keys:
-            - v2-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v2-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run: yarn lint:check
       - run: yarn test:typescript