no-extraneous-dependencies: multiple packageDir(s)

[benmosher]

Continuation of @hulkish's work on #1016, but removes import/paths setting and instead supports both a single string or an array of string paths for the existing packageDir option.

Closes #1016.
Closes #1053.
Closes #935.
Closes #458.

[benmosher]

@hulkish: does this still solve your problem? any reason(s) the enhanced rule option is less desirable than a global setting?

[coveralls]

Coverage increased (+0.02%) to 96.507% when pulling 5111c79 on packageDir-array into 4e37dbf on master.

[ljharb]

this was unused, but i just fixed a use of hasOwnProperty in master, so this line should be reverted

[benmosher]

done, thanks for the tip

[dan-kez]

@benmosher Thanks for this! Can we publish a new release to npm with this change please? Looking forward to using it

[benmosher]

working on it, wanted to get #1091 in as well, but I suspect I'll have it out this week

[dan-kez]

Hey @benmosher just wanted to check in about a new release as #1091 was merged in.

Thanks again!

[dvsekhvalnov]

Hi @benmosher and @hulkish ,

Wanted to check. The given patch doesn't seem to 'merge' multiple package.json declared in packageDir array together, but rather picks up 'rightmost' package.json from array?

At least latest published v2.12.0.

[hulkish]

@dvsekhvalnov correct, this fixes it: #1104

just waiting for review

[dvsekhvalnov]

Thank you !