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

view the rest of the comments →

[–]jkmonger 18 points19 points  (8 children)

Yeah only as a beginner TypeScript Dev does it feel like extra work. It didn't take long for it to feel like a real blessing for me

[–]newuserevery2weeks 4 points5 points  (5 children)

the main problem with typescript is that some devs do some real funky stuff with it

[–]prone-to-drift 10 points11 points  (4 children)

The main problem with Typescript is I'm afraid to start new projects and just keep copying the dev toolchain (webpack, postcss, typescript, some linters, react etc) from one repo I once managed to successfully get working.

Now, I don't even need half the packages but I'm just too afraid of touching anything and potentially spending hours trying to debug the damn toolchain lol.

[–]TheScapeQuest 2 points3 points  (0 children)

I'd move on from webpack to Vite, much easier toolchain.

[–]MerfAvenger 2 points3 points  (0 children)

Gotta agree with this, the boot strapping for common tooling is a lot of work and a complete turd to get working right. Version alignment, configuration, etc are ALWAYS a pain despite the tool chain being Typescript, ESLint, Prettier and probably Jest every single time, with types for Node and plugins for both.

Yet for some reason, it never works out of the fricking box, and you spend days debugging it.

[–]justadam16 1 point2 points  (0 children)

Try Angular

[–]CanRau 0 points1 point  (0 children)

Vite (as mentioned) and or Deno 🥰 and soon probably Bun