Go to definition, auto complete, very slow in VSC March 2019 release w/ Styled Components

I’m not sure where this belongs but it does appear to be an issue of interaction between vscode-styled-components and the latest “March 2019” release of VSC.

Here are some examples:

Go to definition triggers the file header loading bar for 2-3 seconds before yielding the go-to-definition “pop-up” screen. Reverting to February makes everything snappy again (millseconds):

Auto complete takes a few seconds of “Loading…” in March release while typing attributes inside of a styled component’s JSX. After reverting to February release everything take milliseconds again.

Am I doing something wrong? Any ideas? More info needed?

I tried doing verbose logging around electron_node tsserver.js which is showing the high CPU when this happens (I followed the guide here: https://github.com/Microsoft/vscode/issues/63630#issuecomment-442690063) but as not seeing any errors. The logs did confirm that things were taking multiple seconds to come back from tsserver during the above 2 situations (and NOT on older versions of VSC).

[Jaymun723]

I experience lag with styled component and found that @types/styled-component depends on @types/react-native which makes conflicts with the “dom” lib in typescript. The lag was gone when I uninstall @types/styled-component and replace it with a simple module declaration (declare module 'styled-component').

[johnculviner]

Hey thanks, glad to see it isn’t just me. Hopefully this will get fixed soon in VSC. I say we leave this open until it is just so people see it?