Felix Kling
Felix Kling
So this would be another parser that can be selected from the settings? 
I think this is a great idea and should absolutely do it! The way astexplorer works atm though would make this a bit weird to implement. Coincidentally I'm currently working...
Oh interesting. I will have to look into that, I like that idea a lot. Is typescript bundled into a single file or how do you load it from unpkg?...
@andrewbranch sorry for the late reply and no worries. I have been thinking a lot about this, but haven't come up with a good solution yet. Maybe I'm just stuck......
I guess I should "blacklist" global variables :wink:
Unfortunately this works "as designed". The selected parser isn't connected to the selected transformer at all. I have plans to change this though.
So, am I correctly understanding that this is the JavaScript parser generated by tree sitter? I see that it supports various languages. Does that mean we could also add a...
Yes :D
That's an issue with the current design of astexplorer. The parser and the transform are completely independent, i.e. selecting the typescript-eslint parser won't actually make the eslint *transform* use that...
Sounds like a good idea to me!