Discussion on: The TypeScript Experience

View post

import { OldComponent as _OldComponent } from 'components';
const OldComponent: any = _OldComponent;

I won't lie, there are things I really like with TS, but I wish I could spend less time making the compiler happy.

If someone wants to make a sound type system for ES6+, I'm all-in for it… 😂

Rense Bakker • Apr 14 '22

Why on gods earth would you do that?

Etienne Burdet • Apr 14 '22

Because OldComponent is not typed (and we don't want to type it now), so it creates problem with types of children, spread props etc.

Rense Bakker • Apr 14 '22

Not sure how that is possible? Afaik if you can import your untyped js code like that, typescript is going to infer types from it as well... If it's an untyped module and type inference is not possible for some reason, you can use something like this:

// components.d.ts
declare module 'components' {
  export const OldComponent:any
  // or just give it a proper type asuming its a react component?
  export const OldComponent:() => JSX.Element
}