<p dir="auto">For linting files.</p>
<p dir="auto">Probably should be implemented similar to how we've done <code class="notranslate">--fmt</code> ... that is get eslint into deno_std, and then load from URL in core.</p>
<p dir="auto">Right now for npm specifiers, we sort the npm package requirements by name only and then resolve them. This is ok for specifiers with different names, but not when they match. Instead we should probably resolve npm specifiers with the same name by module depth. This would allow npm specifiers with the same name closer to the user to have higher precedence than those at a lower tree depth in remote modules for example.</p>
<p dir="auto">I will open a PR for this after landing the peer dependency support because resolution has undergone a lot of changes.</p>