-
Notifications
You must be signed in to change notification settings - Fork 190
Issues: webpack/enhanced-resolve
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
ESM: Resolving to the wrong package with
exports
and nested same package but different versions
#399
opened Dec 22, 2023 by
Boshen
AliasPlugin crash when file is deleted or rename (have to restart to make it work)
#395
opened Aug 23, 2023 by
zecka
Exports field trees with top-level conditions result in a misleading error message
#325
opened Jan 12, 2022 by
Sidnioulz
NormalModuleFactory.afterResolve is no longer a waterfall hook
#248
opened Sep 21, 2020 by
robatwilliams
modules in node_modules not resolved when using lookupStartPath "."?
#231
opened Jul 15, 2020 by
sverweij
ProTip!
Add no:assignee to see everything that’s not assigned.