emotion-js/emotion

Rewrite to TypeScript

Open

#2,358 opened on Apr 26, 2021

View on GitHub
 (26 comments) (19 reactions) (0 assignees)JavaScript (1,091 forks)batch import
TypeScriptfeature requesthelp wanted

Repository metrics

Stars
 (17,141 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Since Flow is not actively used by any core contributor and its adoption in the community has dropped significantly (especially in comparison to its alternative) it's time to refactor the codebase from Flow to TypeScript.

We could use some help with that. It's best to start from the small, leaf packages. We already have TS types for our packages, they are just not generated from the source.

Progress

  • babel-plugin
  • babel-plugin-jsx-pragmatic
  • babel-preset-css-prop
  • cache
  • css
  • css-prettifier
  • eslint-plugin
  • hash
  • is-prop-valid
  • jest
  • memoize
  • native
  • primitives
  • primitives-core
  • react
  • serialize
  • server
  • sheet
  • styled
  • unitless
  • utils
  • weak-memoize

Contributor guide

Research direction
Start with leaf packages listed in the issue, convert Flow types to TypeScript, and ensure existing tests pass.
Tech stack
javascripttypescript
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptGitknowledge of the emotion codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30