docs(getting-started): include a section about adding hammerjs to the config types

[crisbeto]

Adds a section to the docs, mentioning that the user needs to add hammerjs to the tsconfig.json, in order to avoid some compilation errors.

Fixes #1944.

[clydin]

This shouldn't be necessary. See:
https://www.typescriptlang.org/docs/handbook/tsconfig-json.html#types-typeroots-and-types

[clydin]

With the caveat of already having a types setting

[crisbeto]

It seems like it is, on our local demo test site we have the typeRoots everywhere, but it breaks if I remove the types setting.

[clydin]

Interesting. In my CLI-based projects I don't actually need either setting and I have a large amount of types installed.

[jelbourn]

LGTM

[clydin]

I looked at the demo app. tsc can resolve hammerjs after removing both typeRoots and types. (You will however get an error about a duplicate definition for "module"; @types/node defines it).
The issue appears to be the gulp typescript plugin.

[clydin]

Confirmed. Upgrading and integrating the latest gulp typescript plugin fixes the type resolution issue.
However, for material's repo structure and the large amount of gulp related @types, it would be better to leave the types setting in this case to restrict the included types to only hammerjs.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}