title: How to fix import / no-unresolved eslint to look at package.json "module" instead of "main"
body: <p>I'm currently importing a yarn workspace package that has the <code>module</code> field defined in ES6 and linting with the plugin <code>eslint-plugin-import</code></p>
  
  <p>My create-react-app setup automatically uses the <code>module</code> through webpack but eslint is complaining that <code>@mycompany/utils</code> package is undefined.   </p>
  
  <p><code>Unable to resolve path to module '@mycompany/utils'. [import/no-unresolved]</code></p>
  
  <blockquote>
    <p>So my question is how do I get my linter to look at the <code>module</code> path instead of <code>main</code></p>
  </blockquote>
  
  <p>This is my package.json for the utils package</p>
  
  <pre><code>{
    "name": "@mycompany/utils",
    "version": "0.0.2",
    "main": "dist/index.js",
    "module": "src/index.js"
  }
  </code></pre>