Configure `tsconfig.json` to only load `@types/node` for Node programs

Configure tsconfig.json to only load @types/node for Node programs, and not to pollute code which runs on the browser with the following types.

Issue brought up in https://github.com/jpmorganchase/modular/pull/8#discussion_r428988654 and https://github.com/jpmorganchase/modular/pull/1#discussion_r428815379 (although the latter is more from ESLint’s perspective).

I suspect ‘solution-style tsconfig.json’ are the right approach but these are very new so might lack support.

[sebinsua]

@sanjayk I will not let anybody write code which looks like C# or Java. Trust me! 😆

(I like to write TypeScript code which is basically like simplistic JavaScript, to avoid complicated types and to try to only put types on function arguments and returns instead of interleaving them all over the place.)

[sebinsua]

My perspective is that we can make the code-base better by using TypeScript. Easier to understand, easier for others to contribute to, etc.

Does an excellent JavaScript engineer need TypeScript to help them refactoring some code? Generally not.

However, I’ve worked on JavaScript projects before with 100s of files, where refactoring caused lots of runtime errors that I had to painstakingly fix one-by-one. It is much easier to do this with a type-checker: you can often do what would have otherwise been extremely difficult refactors that might have taken a week or so or in just a day. Static typing is also a useful tool for power users.