Change recommended configuration so that the typescript-eslint-parser is only used for import plugin rather than globally

Presumably this is being used while people convert over to TypesScript, so scoping it to the individual plugin settings can prevent unrelated issues from popping up. We noticed some additional errors when changing the global parser, so this was the fix that worked in our case and follows the structure from the`eslint-plugin-import` docs https://github.com/benmosher/eslint-plugin-import#importparsers

Author: fuller

Diff for: README.md

@@ -21,13 +21,15 @@ Add the following to your `.eslintrc` config:
 
 ```CJSON
 {
-  "parser": "typescript-eslint-parser",
   "plugins": ["import"],
   "rules": {
     // turn on errors for missing imports
     "import/no-unresolved": "error"
   },
   "settings": {
+    "import/parsers": {
+      "typescript-eslint-parser": [".ts", ".tsx"]
+    },
     "import/resolver": {
       // use <root>/tsconfig.json
       "typescript": {},
@@ -41,6 +43,7 @@ Add the following to your `.eslintrc` config:
 }
 ```
 
+
 ## Contributing
 
 - Make sure your change is covered by a test import.