A few tips in order
- restart the terminal
- restart the machine
- reinstall nodejs + then run
npm install typescript -g
If it still doesn't work run npm config get prefix to see where npm install -g is putting files (append bin to the output) and make sure that they are in the path (the node js setup does this. Maybe you forgot to tick that option).
A few tips in order
- restart the terminal
- restart the machine
- reinstall nodejs + then run
npm install typescript -g
If it still doesn't work run npm config get prefix to see where npm install -g is putting files (append bin to the output) and make sure that they are in the path (the node js setup does this. Maybe you forgot to tick that option).
You are all messing with the global installations and -path files. Just a little error might damage every project you have ever written, and you will spend the rest of the night trying to get a console.log('hi') to work again.
If you have run npm i typescript --save-dev in your project - just try to run:
npx tsc
And see if it works before messing with global stuff (unless of course you really know what you are doing)
Typescript tsc does nothing
Typescript: This is not the tsc command you are looking for
Do you use tsc in a production environment? Seems like everyone uses a third-party transpiler.
pro-tip: if you constantly need to restart tsc/eslint, adjust VSCode memory settings : typescript
Videos
» npm install typescript
I'm wondering what the use-cases are for tsc as a transpiler, since it seems like almost everyone uses a third-party one. I'd prefer to use tsc instead of relying on an additional dependency, but find it too restrictive. This has me wondering: who does use it?
To be clear: I understand the use-case for tsc as a type-checker, just not as a transpiler.
Edit: I should have specified: this question is about transpiling with tsc for front-end code, not back-end code.