Closed Korywon closed 5 months ago
Also seeing this - perhaps related to b66d19b9b6ec3edf3d8aff0c20646acbdaa0afb3
I noticed that import type { ... } 'package'
works just fine, but doing import { type PackageType } from 'package'
is what breaks it.
o dear, this is open since April 26? anything I can do to help get this fixed?
for me this issue still persists, or is there a way to get the newer version, :TSUpdate won't do
T-T
seems fine on master. let me know of parse errors if not
its happening to me
The following piece of code is valid but it is parsed incorrectly:
Screenshot of the bug I'm seeing:
Here's a link to the TypeScript Playground showing that the snippet above is valid JavaScript or TypeScript: https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzjAnmApnAgmMAVAQwCM4BfOAMyghDgHIABAelQwGc6AoUSWRTuHABCAVxgwIAOwA0AuAHEowACazBilQEkY6EGrgi26ACLA2AYwA2ENiKjpO5KjXoNzACwIBrKAQC0IsBM9gTmMFxAA
The output of
tree-sitter parse
is the following:I was expecting the parser to not expect
=
after the variable. When wrote=
in front of my import, it seems to fix the highlighting. FWIW, I am using Astrovim.https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html