Fix hooking parent and sub module with a single hook

[pgayvallet]

Fix #79

Fix the bug causing a hook used for both a module and some of its sub module to only hook into the parent module.

new Hook(['sub-module/foo', 'sub-module'], handler)

[gsoldevila]

LGTM!

[trentm]

Suggested change

	if (modules.includes(fullModuleName)) {
	if (modules.includes(fullModuleName) && moduleName !== fullModuleName) {

This all looks good. I can't break it. :)

One thing that was niggling me a little bit is this one case. If moduleName === fullModuleName -- e.g. when doing require('sub-module') -- then this would result in (a) the isWhitelistedSubmodule === true being slightly misleading and (b) the if (!isWhitelistedSubmodule) { ... block below being skipped. However, I can't come up with a case where skipping that block isn't just fine -- I expect res === filename every time that happens.

tl;dr: What you have here works, as best I can tell, but I think I'd prefer to have this small patch.

[trentm]

Let me know if you have thoughts on the suggestion. Then I can get a release out of this soon.

[pgayvallet]

Yeah, I think you're right: in practice, I'm not sure it's impacting in any way, but I agree that it's still technically better to dissociate that case.

I pushed your suggestion, let me know if you think we need to perform any more changes. Otherwise, I think we're good releasing as soon as you can.