[jest-resolve] Add support for packageFilter for custom resolvers

[scinos]

Summary

Forwards option packageFilter to resolve. This is useful in case a custom resolver wants to use it. The best example is #2702 (in particular, #2702 (comment))

Fixes #2702

Test plan

Write a custom resolver like

module.exports = ( request, options ) => {
	return options.defaultResolver( request, {
		...options,
		...{
			packageFilter: ( pkg ) => {
				return {
					...pkg,
					main: pkg.module || pkg.main,
				};
			},
		},
	} );
};

Then, in any jest test, when importing package X, it will try to load it from the field module first, with fallback to main if module doesn't exist.

[SimenB]

Thanks!

This needs a test and an example in the docs for how this would be used to check the module prop

[scinos]

Full disclosure: I've never used Jest+TS, I don't know if there is a better way of doing this.

[SimenB]

Thanks!

[SimenB]

https://github.com/facebook/jest/releases/tag/v26.4.0

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.