Flow: Named import from module `react` This module has no named export called `Component`.

[neurosnap]

Is there a way to get around this warning?

import { Component } from 'react';

class Something extends Component {}

Named import from module react This module has no named export called Component.

[keplersj]

After updating I'm getting this on the latest flow flow-bin as well

[keplersj]

Hmm... I attempted downgrading Flow to see if this is truly a regression and it doesn't look to be. The issue emerged during a transition from Meteor to next.js.

[nmn]

Cannot reproduce: LINK

[keplersj]

Issue disappears when all libdefs installed with flow-typed are removed. Looking for the troublesome libdef right now.

[keplersj]

The issue come from the next.js libdef from flow-typed. The libdef has a import type { Component } from 'react'; outside of a declare module block. The messes up the type checker in a major nearly untraceable way.

[jsg2021]

Component is not a named export of react. It is a property on the default export... transpilers allow this to work for commonjs modules because of their interop, but it's technically incorrect.

[neurosnap]

My issue was a libdef like @keplersj suggested.

[zachariahtimothy]

I too had this issue on a next.js project as @keplersj mentioned. I downgraded to flow-bin@^0.53.0 and the trouble is gone as done in the este project.