emotion-js · Dec 14, 2018 · Dec 14, 2018 · Dec 15, 2018 · Dec 15, 2018 · Dec 17, 2018
Showing 322 changed files with 18,869 additions and 12,500 deletions.
diff --git a/.changeset/README.md b/.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.
diff --git a/.changeset/config.json b/.changeset/config.json
@@ -0,0 +1,30 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@0.2.1/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"
+}
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -8,11 +8,10 @@ jobs:
       - checkout
       - restore_cache:
           keys:
-            - v3-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v3-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,7 +21,7 @@ jobs:
           paths:
             - ~/.cache/yarn
             - node_modules
-          key: v3-dependencies-{{ checksum "yarn.lock" }}
+          key: v4-dependencies-{{ checksum "yarn.lock" }}
 
   test:
     docker:
@@ -32,9 +31,9 @@ jobs:
       - checkout
       - restore_cache:
           keys:
-            - v3-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v3-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run:
           name: Jest Tests
@@ -55,9 +54,9 @@ jobs:
       - checkout
       - restore_cache:
           keys:
-            - v3-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v3-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run:
           name: Jest Tests
@@ -73,12 +72,11 @@ jobs:
       - checkout
       - restore_cache:
           keys:
-            - v3-dependencies-{{ checksum "yarn.lock" }}
+            - v4-dependencies-{{ checksum "yarn.lock" }}
             # fallback to using the latest cache if no exact match is found
-            - v3-dependencies-
+            - v4-dependencies-
       - run: yarn install --pure-lockfile
       - run: yarn lint:check
-      - run: yarn test:typescript
 
 workflows:
   version: 2

diff --git a/.flowconfig b/.flowconfig
@@ -1,12 +1,13 @@
 [version]
-0.81.0
+0.110.0
 
 [ignore]
 .*/node_modules/config-chain/.*
 .*/node_modules/styled-components/.*
 .*/node_modules/graphql/.*
 .*/node_modules/metro.*
 .*/node_modules/preact/.*
+.*/node_modules/@parcel/.*
 
 [untyped]
 .*/node_modules/polished/.*
@@ -22,11 +23,5 @@
 
 [options]
 suppress_comment=.*\\$FlowFixMe
-module.name_mapper='^\(create-emotion\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(emotion\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(babel-plugin-emotion\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(emotion-theming\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(emotion-server\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(create-emotion-server\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^\(jest-emotion\)$' -> '<PROJECT_ROOT>/packages/\1/src'
-module.name_mapper='^@emotion\/\([a-zA-Z0-9_\-]+\)$' -> '<PROJECT_ROOT>/packages/\1/src/index'
+suppress_comment=.*\\$FlowExpectError
+sharedmemory.hash_table_pow=21
diff --git a/.flowconfig-ci b/.flowconfig-ci
@@ -0,0 +1,29 @@
+[version]
+0.110.0
+
+[ignore]
+.*/node_modules/config-chain/.*
+.*/node_modules/styled-components/.*
+.*/node_modules/graphql/.*
+.*/node_modules/metro.*
+.*/node_modules/preact/.*
+.*/node_modules/@parcel/.*
+
+
+[untyped]
+.*/node_modules/polished/.*
+
+
+[include]
+
+[libs]
+
+[declarations]
+.*/node_modules/react-native/.*
+
+
+[options]
+suppress_comment=.*\\$FlowFixMe
+suppress_comment=.*\\$FlowExpectError
+server.max_workers=1
+sharedmemory.hash_table_pow=21
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: emotion
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
diff --git a/.github/ISSUE_TEMPLATE/--bug-report.md b/.github/ISSUE_TEMPLATE/--bug-report.md
@@ -0,0 +1,47 @@
+---
+name: "\U0001F41EBug report"
+about: Something isn’t working as expected
+title: ''
+labels: bug, needs triage
+assignees: ''
+---
+
+<!--
+    Thanks for your interest in the project.
+    Please make sure that you are familiar with and follow the Code of Conduct
+    for this project (found in the CODE_OF_CONDUCT.md file).
+
+    Please fill out this template with all the relevant information so we can
+    understand what's going on and fix the issue.
+
+    I'll probably ask you to submit the fix (after giving some direction).
+    If you've never done that before, that's great! Check this free short
+    video tutorial to learn how: http://kcd.im/pull-request
+-->
+
+**Current behavior:**
+
+<!-- A clear and concise description of what the bug is -->
+
+**To reproduce:**
+
+<!--
+    Please edit this CodeSandbox (https://codesandbox.io/s/zljgy)
+    to help us reproduce your issue. Alternatively, create a GitHub repository.
+    Issues without a reproducible example will take longer to get addressed.
+-->
+
+1. ...
+2. ...
+3. ...
+
+**Expected behavior:**
+
+<!-- A clear and concise description of what you expected to happen -->
+
+**Environment information:**
+
+<!-- Provide the `react` and `emotion` or `@emotion/*` packages versions -->
+
+- `react` version:
+- `emotion` version:
diff --git a/.github/ISSUE_TEMPLATE/--documentation-issue.md b/.github/ISSUE_TEMPLATE/--documentation-issue.md
@@ -0,0 +1,29 @@
+---
+name: "\U0001F4D6Documentation issue"
+about: The documentation is unclear, missing informations, or could be improved
+labels: documentation, needs triage
+assignees: ''
+---
+
+<!--
+  Documentation issues are a great way for newcomers to contribute to
+  open source projects! If you have time please consider opening a
+  Pull Request with your documentation changes.
+-->
+
+**Description:**
+
+<!--
+  Please provide as much detail as possible about your issue,
+  please refrain from asking for solutions to specific problems
+  with your code. This template is to report issues with the
+  official Emotion documentation.
+-->
+
+**Documentation links:**
+
+<!--
+  If existing documentation is available, but needs to be improved,
+  is wrong, or unclear, please post here the relevant 
+  https://emotion.sh/docs URLs
+-->
diff --git a/.github/ISSUE_TEMPLATE/--feature-request.md b/.github/ISSUE_TEMPLATE/--feature-request.md
@@ -0,0 +1,24 @@
+---
+name: "\U0001F680Feature request"
+about: I have a suggestion (and might want to implement myself)
+title: ''
+labels: feature request, needs triage
+assignees: ''
+---
+
+
+**The problem**
+
+<!-- A clear and concise description of what the problem is. e.g. I'm always frustrated when [...] -->
+
+**Proposed solution**
+
+<!-- A clear and concise description of what you want to happen. Add any considered drawbacks. -->
+
+**Alternative solutions**
+
+<!-- A clear and concise description of any alternative solutions or features you’ve considered. -->
+
+**Additional context**
+
+<!-- Add any other context or screenshots about the feature request here. -->
diff --git a/.github/ISSUE_TEMPLATE/--support-question.md b/.github/ISSUE_TEMPLATE/--support-question.md
@@ -0,0 +1,15 @@
+---
+name: "\U0001F914Support question"
+about: I have a question or don’t know how to do something
+title: '[SUPPORT] This will be closed'
+labels: invalid
+assignees: ''
+---
+
+This repository is dedicated to development only activities, if you have questions,
+please use [Stack Overflow](https://stackoverflow.com/questions/ask?tags=emotion).
+
+You may also want to look for existing issues
+in the [issues tracker](https://github.com/emotion-js/emotion/issues).
+
+Thank you for your cooperation!
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -30,5 +30,7 @@ merge of your pull request!
 - [ ] Documentation
 - [ ] Tests
 - [ ] Code complete
+- [ ] Changeset <!-- This is necessary if your changes should release any packages. Run `yarn changeset` to create a changeset -->
+
 
 <!-- feel free to add additional comments -->