Use resolved package name

[mieszko4]

Should fix #496

[ljharb]

Can you add a test case that would have failed without this change?

[coveralls]

Coverage increased (+2.8%) to 97.268% when pulling e25180c on mieszko4:patch-1 into ebafcbf on benmosher:master.

[mieszko4]

@ljharb I've added the test that would have failed without fix in no-extraneous-dependencies.js. Please take a look.

[benmosher]

I'm a little nervous about letting node_modules sneak into a rule proper, though to be fair no-extra-deps is a Node-specific rule.

I'll try to come back around to this in a second pass after letting it cook in my brain for a little bit.

[ljharb]

@arcanis i'm intending to merge this soon, does it need any changes to avoid causing berry problems?

[arcanis]

From the look of it it should be compatible in most cases, since we store packages inside a standalone node_modules path (to make vendor detection easier):

/app/.yarn/cache/foo-1.0.0.zip/node_modules/foo/index.js

One caveat however: we cannot do that when people use the workspace:, link:, or portal: protocol, because they are resolved to the final path. So given the package.json:

{
  "dependencies": {
    "foo": "link:./foo"
  }
}

You'd have /app/foo, not /app/node_modules/foo.