Migrate to import * as React from 'react'

[TrySound]

What:

Migrated to import * as React from 'react'

Why:

Ref facebook/react#18102

This is the recommended way to import react now.

How:

With the help of replace-in-files-cli package

Checklist:

• Documentation
• Tests
• TypeScript Types
• Flow Types
• Ready to be merged
  

[silviuaavram]

Shouldn't we get warning from React? I don't see this being enforced. And could not tell from that issue if it's something that brings any value. Can you describe this a bit so we can have more context? Thank you!

[TrySound]

I don't think it's easy to add warning before migrating to esm.

There is a value with bundlers like rollup when target format is esm.

When bundle apps you get optimisable output with named exports

import { e as createElement } from 'react';
createElement('div')

Default exports leads to hard member expression which can be optimised by babel or webpack plugins but not in natural way

import React from 'react';
React.createElement('div')

[oliviertassinari]

@silviuaavram They might be a bit more context in mui/material-ui#19802.

[silviuaavram]

Understood :) will merge this, thank you!

[silviuaavram]

🎉 This PR is included in version 5.0.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀