emotion-js/emotion

Rewrite to TypeScript

Open

#2358 opened on Apr 26, 2021

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

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

Tech stack
typescriptjavascriptreact
Domain
developer experiencetooling
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
Flow syntaxTypeScript syntaxemotion package structuremonorepo workflow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Focus on leaf packages listed as unchecked in the progress checklist (e.g., babel plugin, cache, css prettifier, jest, memoize, native, primitives, react, server, styled). Review completed packages like css, eslint plugin, hash, etc. for an example of the expected conversion pattern. Check the issue comments (26 total) for any additional guidance or discussions about the approach. Note that the repository already has TypeScript definitions, but they are not generated from source; the goal is to replace Flow source with TypeScript source.