uglycoyote

@cocowalla Thanks for the tip about `global.json`, it seems to have built (On Ubuntu in WSL) when I changed the version there to my installed version of `2.2.401`. The tests...

@cocowalla Thanks for your super-duper-honest reply! Yes after banging my head against this in a few separate sessions, it might be best to take a step back and re-evaluate. My...

I'm not sure what you mean, but I have already established that adding a trailing slash does help with the problem. Adding the trailing slash manually to the URL, when...

@mahagr Thanks for your tip about the `` tag. I was not aware of that mechanism for changing the base URL that all relative URL's are relative to. So I...

Thanks for commenting, though since it has been two weeks since posting this issue it doesn't seem that anyone else thinks this is a critical issue to fix.

I confirm as of April 2020 I'm getting the same issue on a type alias, where it reports `Unexpected token, expected ";"`. Sad that there hasn't been any improvement in...

Investigating this a bit further, it seems like a workaround is to avoid using `localhost` in the launch.json, but instead use the IP of the WSL instance directly: from https://docs.microsoft.com/en-us/windows/wsl/compare-versions#accessing-network-applications...

@garemoko I'm only really using the one LRS (CornerStone OnDemand) so I don't know whether it's a problem with others. I think it's entirely just a question of what headers...

Thanks for the response. By "types of the functions" i meant not just the return type, but really the whole signature. For the callbacks, obviously the return type is uninteresting...

@brianjmiller I have a fair amount of my own Typescript definitions now that I'm using alongside this library, to help make sense of it, so if you do start down...