TypeScript: tsc command not working in 3.2.1 - Expected identifier
TypeScript Version: 3.2.1
Search Terms: Expected identifier
Code
// Start a command line and just write tsc or tsc -v
Expected behavior: display the current version or the info
Actual behavior: It raises a Windows Script Host error (check image)

I checked the installation folder and there is just a tsc.js file. The tsc.exe is missing
The npm works fine. It is the TypeScript_SDK.exe for VS 2017 what fails.
Playground Link:
Related Issues: SO: Windows 10 1809 10.0.17763.107
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 23 (9 by maintainers)
Yes we removed
tsc.exein 3.2 so this exact method of invocation wouldn’t work anymore. A command likenode.exe full_path_to_tsc.jswould work.What is your exact scenario and goal here? We may need to update some docs depending on what you’re trying to achieve.
We stopped shipping
tsc.exein the SDK AFAIK - @minestarks ?Our CI server runs Node 8, 10, and 11, though we were running Node 6 as well until very recently. So 8 / 10 / 11 are “officially” supported in that regard and I’d expect Node 6 to “happen to work” for at least a little while longer.
If something did break on an unsupported version, it would be fairly obvious (e.g. crash); we’ve never had a “different output” situation from varying node versions. So you’re fairly safe running any version which appears to work.
@minestarks Is there some documentation on how to migrate from the old
tsc.exe --argscommand tonode.exe tsc.js --argscommand?Thanks for the info. I was just trying to check wether the PATH was pointing to the correct folder or not. So this “issue” is not something that blocks any kind of project I am doing at the moment.