Redirect module requests.
Fields in the description file (usually package.json) which are used to redirect requests inside the module.
Extra resolve options per dependency category. Typical categories are "commonjs", "amd", "esm".
Enable caching of successfully resolved requests (cache entries are revalidated).
Include the context information in the cache identifier when caching.
Condition names for exports field entry point.
Filenames used to find a description file (like a package.json).
Enforce the resolver to use one of the extensions from the extensions option (User must specify requests without extension).
Field names from the description file (usually package.json) which are used to provide entry points of a package.
An object which maps extension to extension aliases.
Extensions added to the request when trying to find the file.
Redirect module requests when normal resolving fails.
Filesystem for the resolver.
Treats the request specified by the user as fully specified, meaning no extensions are added and the mainFiles in directories are not resolved (This doesn't affect requests from mainFields, aliasFields or aliases).
Field names from the description file (usually package.json) which are used to provide internal request of a package (requests starting with # are considered as internal).
Field names from the description file (package.json) which are used to find the default entry point.
Filenames used to find the default entry point if there is no description file or main field.
Folder names or directory paths where to find modules.
Plugins for the resolver.
Prefer to resolve server-relative URLs (starting with '/') as absolute paths before falling back to resolve in 'resolve.roots'.
Prefer to resolve module requests as relative request and fallback to resolving as module.
Custom resolver.
A list of resolve restrictions. Resolve results must fulfill all of these restrictions to resolve successfully. Other resolve paths are taken when restrictions are not met.
A list of directories in which requests that are server-relative URLs (starting with '/') are resolved.
Enable resolving symlinks to the original location.
Enable caching of successfully resolved requests (cache entries are not revalidated).
Use synchronous filesystem calls for the resolver.
Predicate function to decide which requests should be cached.
Options object for resolving requests.