Added typescript@next work-around for node_modules

[cartant]

Initial attempt at a work-around for typescript@next to avoid re-compilations for each cache miss on files in node_modules - see #172.

[cartant]

This seems to work okay with typescript@next, but it doesn't work with typescript@beta - as the latter simply refuses to emit anything under node_modules, regardless of the roots passed to createProgram. According to this comment, the change that should fix the beta has been merged with the 2.0.0 release.

[tgrecojs]

@cartant this may be a "stupid" question, but what is the inherent difference between installing typescript@beta vs typescript@next?

[cartant]

@thomasjosephgreco Not a stupid question at all. If you run npm info typescript, you'll see the versions installed in the dist-tags:

{ name: 'typescript',
  description: 'TypeScript is a language for application scale JavaScript development',
  'dist-tags': { latest: '1.8.10', next: '2.1.0-dev.20160808', beta: '2.0.0' },

So typescript@beta is installing the current 2.0.0 beta release and typescript@next is installing what is essentially the current master - a nightly build. (I find it pretty confusing that the beta's semver is not a pre-release. That is, it's not something like 2.0.0-beta.)

If you want to see what the differences between 2.0 and 2.1 will be, there is the roadmap.

[cartant]

It seems that this comment is correct and the fix has been incorporated into the TypeScript 2.0 RC.