webpack / enhanced-resolve

Offers an async require.resolve function. It's highly configurable.

webpack/enhanced-resolve Issues

ESM: package.exports array target not conforming to the ESM specification
Updated 3 months ago10
Add ability to handle win32 relative paths
Updated 3 months ago4
ESM: Resolving to the wrong package with `exports` and nested same package but different versions
Updated 4 months ago3
is this possible with webpack AliasPlugin to automatically switch to a different alias when original file is deleted?
Closed 4 months ago7
Seeing "Error: No file content" for different package.json files when webpack rebuilds
Closed 4 months ago1
AliasPlugin crash when file is deleted or rename (have to restart to make it work)
Updated 8 months ago
enhanced-resolve is broken on Windows
Closed a year ago5
Hooks do not fire events from CSS/SCSS imports
Updated 10 months ago5
`exports.types` after `exports.default`
Closed 10 months ago5
resolving packages entrypoints with a non-standard node_modules
Updated a year ago4
`extensionAlias` is not applied to module exports
Closed a year ago21
Improve the typescript definitions
Closed a year ago1
Use of `extensionAlias` fails resolution of subpath exports in `exports` fields
Closed a year ago2
Exports subpath wildcard patterns issue.
Closed a year ago2
conditionNames defaults to `["node"]` according to docs, but possibly doesn't actually
Closed a year ago2
signature of method `stat` in interface `FileSystem` mismatches.
Closed a year ago2
can't resolve exports pattern startsWith wildcards
Closed a year ago1
bug: exports map key with star in the middle doesn't work
Closed a year ago1
Webpack does not seem to work with nodes subpath imports.
Closed 3 years ago5
add type defines for `CachedInputFileSystem` ?
Updated a year ago5
CachedInputFileSystem OOM when duration is infinity
Updated a year ago5
virtual module not found error
Closed a year ago1
Field 'browser' doesn't contain a valid alias configuration
Closed a year ago2
Latest release broke storybook
Closed a year ago11
Use throwIfNoEntry for sync resolver once graceful-fs supports it
Closed a year ago1
Could not resolve "pnpapi" with Webpack 5.74.0
Closed a year ago1
Show more information when resolve exports field failed
Closed 2 years ago4
[Question] The behavior of importsField conflicts with `require.resolve`
Closed 2 years ago6
Resolving to browser entrypoint
Closed 2 years ago1
About the new change in AliasPlugin.js
Closed 2 years ago3
Unable to resolve named module to in the current directory in Webpack 5
Closed 2 years ago6
When package xxx supports 'exports' and 'types', 'xxx/types' import leads an error
Closed 2 years ago2
resourceQuery appending to package from node_modules result to wrong module request
Closed 2 years ago4
why `.mjs` import a different file with other in webpack4
Closed 2 years ago7
Exports and `conditionNames` matching
Closed 2 years ago3
`webpack` fails to resolve `@rollup/plugin-json` (`TypeError: json is not a function`)
Closed 2 years ago3
Is it possible to find the "first" issuer of a `request`?
Closed 2 years ago1
[help request]
Closed 2 years ago2
Exports field trees with top-level conditions result in a misleading error message
Updated 2 years ago10
Support typescript@4.5 `.js` import extension requirement
Closed 2 years ago4
Problem with exports
Updated 2 years ago5
Support `node:http` etc.
Updated 3 years ago3
RootsPlugin causes watchpack watches a set of wrong paths
Closed 3 years ago24
Subpath imports don't work for built-in Node modules
Updated 3 years ago4
Promise api
Updated 3 years ago1
Resolving root path in RootsPlugin
Updated 3 years ago11
`exports` and `node_modules` inside package resolving broken
Closed 3 years ago4
[Question] Support for nested conditions
Closed 3 years ago12
Callback for whether `unsafeCache` was used to respond to a request
Updated 3 years ago
How to reuse webpacke resolve inside another package configuraiton
Updated 3 years ago4