Add tsconfig files to the appropriate repos

[samreid]

For the feasibility prototype, tsconfig files have been aggregated in chipper. However, it is more appropriate to put the tsconfig files in the corresponding repos. I have avoided doing this until now since I didn't want to introduce any overhead or burden on JavaScript development. But @jonathanolson and I discussed it today, and think we can go ahead and do this. The only burden that we are aware of is that navigation in WebStorm will take you to the phet-types.d.ts file for assert/lodash/etc, instead of navigating to the files for those. But we realized that is also the long-term expected behavior.

[samreid]

In Slack, I said:

Do you think #1070 would be too disruptive to Fourier development?

@pixelzoom said:

I don’t know. Are you proposing to just add tsconfig files to each repo, or to turn on the new “TypeScript aware” build tools?

I replied:

Just the config files
Would it be OK if we add one or two, to make sure it doesn’t hamper JavaScript development? Then if it doesn’t hamper JavaScript development, we can add all of them?

@pixelzoom said:

Seems reasonable.

[samreid]

In the commits, I moved circuit construction kit common's tsconfig file to master. I'll use that for testing over the next few days (without typescript) to see if it hampers workflow in any way.

[samreid]

I worked with @zepumph on CCK with tsconfig in master for more than an hour and did not observe any problematic effects.

[samreid]

In discussion today, @jonathanolson advocated for combining tandem and axon repos, since they have so much crossover. I'm reluctant to do so--it seems there are some good separation of concerns and attempted modularity that would be good to keep.

But we agreed it is OK to start moving tsconfig files out to individual repos.

[samreid]

I can't get much further on #1073 without adding the tsconfig files to master, I'll start that soon.

[samreid]

I've moved all the tsconfig to their corresponding repos. One note that these tsconfig files only include the core code for that repo, and not any of the tests. Tests often include downstream dependencies. For instance, the joist demo imports modules from sun and scenery-phet. So adding a dependency on joist means a dependency on joist but without its tests (and those transitive dependencies).

I'll open a new issue for how to do the test tsconfigs.

[samreid]

The tsconfig files have been moved to master. I tested some grunt output-js and grunt output-js-project and grunt output-js-all and they are working as expected. Closing.