Plugin incompatible with Node.js exports package.json field

[ctavan]

This plugin tries to resolve the package.json files of processed modules:

rollup-plugin-svelte/index.js

Lines 177 to 180 in 85d25fb

	const resolved = tryResolve(
	`${name}/package.json`,
	path.dirname(importer)
	);

This breaks with npm modules that make use of the new exports field but do not specify a subpath export for the package.json file.

This issue surfaced in uuidjs/uuid#444

IMO this plugin can no longer expect that every npm module exports the package.json file and the resolver logic has to be adjusted accordingly.

Maybe in

rollup-plugin-svelte/index.js

Lines 48 to 55 in 85d25fb

	function tryResolve(pkg, importer) {
	try {
	return relative.resolve(pkg, importer);
	} catch (err) {
	if (err.code === 'MODULE_NOT_FOUND') return null;
	throw err;
	}
	}

we could add ERR_PACKAGE_PATH_NOT_EXPORTED as an "acceptable" error as well?

[jpaquim]

I was having the same problem with the uuid package, and implemented this PR #108 as a workaround.

I only saw this discussion afterwards, but it seems like it follows in the direction you mentioned, of making it an acceptable error. I could use some feedback on the actual implementation though, there's probably a better way of getting the resolved file name other than parsing the error message.

[maxdobeck]

Another example: https://github.com/bvaughn/js-search

[!] (plugin svelte) Error: Package subpath './package.json' is not defined by "exports" in /home/.../node_modules/js-search/package.json

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './package.json' is not defined by "exports" in /home/.../node_modules/js-search/package.json

[zwz]

And here is another one: marijnh/w3c-keyname#10