I honestly think web development is getting harder ...

gistfile1.txt

Expanding on the sentiments of this tweet: https://twitter.com/ColinEberhardt/status/1048099572537548800

"I honestly think web development is getting harder. We have some amazing and innovative tools / frameworks, but
their loosely-coupled nature results in fragility. And when things go wrong, you need a surprising depth of
knowledge to resolve the issue."

Here's a a list of things that went wrong, or were more difficult than I might have anticipated over a short
2 hour period ... when creating a new web project

1. Dependencies that were not on npm
2. TypeScript type definitions in all kinds of inconsistent places (typedef files on npm, projects that ship their own)
3. Out-dated TypeScript definitions that are incompatible with the independently shipped library
4. VSCode needing restarting periodically when TS compiilation was failing
5. VSCode, tsc and WebPack disagreeing on whether the project was error free
6. Webpack's loader model is highly extensible, but complex for simple tasks - 'move my HTML file into the dist folder
7. Sourcemaps, debugging is a fundamental feature of development, but we don't make it easy on ourselves!
8. Node version issues - hello nvm!

... and more besides

For the last point, you might want to try asdf with the node plugin. It works great, and best of all is that you can use the same tool for many other languages as well.

Thanks @cesarandreu - I've not heard of asdf before, I'll take a look!

I agree completely. But just to alleviate (4), you can run the Restart TypeScript Server command in vscode.

I hear you on this.

I also find it's somewhat amusing that my web development workflow is not using any of these items mentioned from 1-8.

I sometimes will use nvm during the process of migrating projects to a newer version of node.