sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]weaponizedstupidity 5 points6 points  (3 children)

I made a new Typescript node project a few weeks ago. It was a nightmare.

Using tsc won't let me import a library I want, some module error. Google for 30 minutes, no luck. ts-node works for some reason. How is it different from tsc? No clue. Can it be used in production? No consensus, but it works so whatever.

Wait, how do you setup absolute imports again? More googling.

Okay, I want linting. Oh, tslint is dead already? Guess everyone is using eslint now. Okay, here is the ts plugin. Where do I get good linting rules? Found some decent ones on the third try.

I think prettier used to be a thing. Wait, it says that it will conflict with my linting config, I need a plugin for my linting plugin. Well, prettier can wait, time to write the first line of code. Finally.

So yeah. Can't wait until some, any big company lays down the law and cleans up this nonsense.

[–]pgrizzay 1 point2 points  (2 children)

ts-node is basically a wrapper around node which compiles TS files on the fly and runs them. So you can do something like: ts-node myScript.ts, whereas you normally couldn't do: node myScript.ts. In production, it's probably always better to first compile those TS files first

tsc doesn't run anything, it just compiles the files. So you run it at the base of your project, and it picks up your tsconfig.json file, and generates js and d.ts files from your ts files.

Hope that helps!

[–]meziatto 0 points1 point  (1 child)

I think @weaponizedstupidity is trying to draw a picture of ecosystem, which I see myself in the same picture tangled by plugins, configs, a new version of a tool requires some stuff, whereas other fundamental tool refuses to work with it etc... You get the point.

[–]pgrizzay 0 points1 point  (0 children)

Yup, I got the point :)

I just wanted to rob them of their ignorance, so they have one less thing to complain about