-
Notifications
You must be signed in to change notification settings - Fork 49.2k
Open
Labels
Component: Build InfrastructureReact Core TeamOpened by a member of the React Core TeamOpened by a member of the React Core TeamType: Breaking ChangeType: Discussion
Description
Currently we only ship CommonJS versions of all packages. However we might want to ship them as ESM in the future (#10021).
We can't quite easily do this because we haven't really decided on what top-level ES exports would look like from each package. For example, does react
have a bunch of named exports, but also a default export called React
? Should we encourage people to import *
for better tree shaking? What about react-test-renderer/shallow
that currently exports a class (and thus would start failing in Node were it converted to be a default export)?
kimjoar, lukastaegert, sjy, nicolasparada, teppeis and 222 moremaraisr, MichielCornilleESC, unrevised6419, johannesklevll, zhangenming and 31 moremashaal, asaxon, silverwind and ThimoDEV
Metadata
Metadata
Assignees
Labels
Component: Build InfrastructureReact Core TeamOpened by a member of the React Core TeamOpened by a member of the React Core TeamType: Breaking ChangeType: Discussion