Unresolved dependencies when "exports" field property's value contains directory match before the correct literal match

[ChrisKuBa]

• Rollup Plugin Name: @rollup/plugin-node-resolve
• Rollup Plugin Version: 11
• Rollup Version: 2.34.0
• Operating System (or Browser): Windows 10 x64
• Node Version: v14.15.0
• Link to reproduction (⚠️ read below): https://repl.it/@chrku/rollup-plugin-repro

Expected Behavior

Successful bundle for packages whose "exports" field in package.json like below:

"exports": {
    "./helpers/": "./helpers/",
    "./helpers/typeof": "./helpers/typeof.js",
    "./helpers/jsx": "./helpers/jsx.js",
    "./helpers/asyncIterator": "./helpers/asyncIterator.js",
    "./helpers/AwaitValue": "./helpers/AwaitValue.js",
...
    "./helpers/objectWithoutPropertiesLoose": "./helpers/objectWithoutPropertiesLoose.js",
...
    "./helpers/esm/extends": "./helpers/esm/extends.js",
...
}

Actual Behavior

Unable to bundle, output like this:

[!] Error: Could not load C:\project\node_modules\react-redux\node_modules\@babel\runtime\helpers\esm\objectWithoutPropertiesLoose (imported by node_modules\react-redux\es\connect\connect.js): ENOENT: no such file or directory, open 'C:\C:\project\node_modules\react-redux\node_modules\@babel\runtime\helpers\esm\objectWithoutPropertiesLoose'

Additional Information

Directory match is preferred over direct file/subpath match, if directory match is configured before subpath match in exports.
This should be a fallback, if no subpatch match exists.

Hint: After removing line 27 - 30 the build was successfully.

plugins/packages/node-resolve/src/resolveImportSpecifiers.js

Lines 27 to 35 in d35a7ea

	if (key.endsWith('/') && subPath.startsWith(key)) {
	// directory match (deprecated by node): "./foo/": "./foo/.js"
	return key;
	}
	if (key === subPath) {
	// literal match
	return key;
	}

[LarsDenBakker]

Looking into this one

[shellscape]

Resolved by #675