Releases: webpack/enhanced-resolve
Releases · webpack/enhanced-resolve
v5.0.0
Features
- increase minimal node.js version
- update dependencies
- remove memory-fs dependency
- real fs is usable, no
join
expected from filesystem - track dependencies while resolving
- add support for arrays in alias
- add support for Yarn PnP
- PnP tracks dependency to the .pnp.js file
- add support for
alias: { something: false }
- generate and publish type declaration file for typescript
exports
field support- add
exportsFields
option - add
conditionNames
option
- add
- self reference resolving when
exports
field is present - add
restrictions
option, which allows to restrict the allowed paths to resolve too - add fragment support
- add
roots
option - add
fullySpecified
option for better node.js esm compat - refactor CacheFileSystem
- allow only sync usage
- support second
options
argument for all methods
- add support for
imports
field in package.json - add new
fallback
option, which is likealias
but is only activated when normal resolving fails
Removals
- remove concord
- remove deprecated tapable compat layer
- remove .context and .loader from node API
- remove NodeJsInputFileSystem
Bugfixes
- fixes lowercase file letters
- fixes
"main": "."
crash - fix purging of readdir
module/
now correctly resolves to directory and not tomodule.js
as file- fix lisence field in package.json
- Fix bug when instead of package resolving in modules file with same name was resolved
Contribution
- refactor join and normalize to use node.js path instead of memory-fs
- linting update
- code style update (spread operator, let/const, arrow functions)
- add a lot of type information
- Linting type information
- Linting formating
Performance
- optimize number of fs accesses
- serialize all operations to reduce number of fs accesses
- deduplicate duplicate entries in
aliasFields
,descriptionFiles
,extensions
,modules
,mainFields
andmainFiles
Internals
- Options are normalized separatly
- improve handling of scoped packages
@scope/name
v5.0.0-beta.12
Bugfixes
- Revert for: Directories starting with
#
are no longer treated as fragment
v5.0.0-beta.11
Features
- add support for
imports
field in package.json - add new
fallback
option, which is likealias
but is only activated when normal resolving fails
Bugfixes
- Directories starting with
#
are no longer treated as fragment - Fix bug when instead of package resolving in modules file with same name was resolved
v5.0.0-beta.9
Features
- add
fullySpecified
option for better node.js esm compat - refactor CacheFileSystem
- allow only sync usage
- support second
options
argument for all methods
v5.0.0-beta.10
Bugfixes
- fix for
resolveToContext
withfullySpecified
v4.3.0
v5.0.0-beta.8
Features
- add
roots
option
v5.0.0-beta.7
Features
- add fragment support
Bugfixes
- handle query and fragment correctly in
exports
field lookup
v4.2.0
Features
- add
restrictions
option- allow to specify strings or regexps that must be matched for a valid result
- when not matched, alternatives are tried (like alternative mainField, mainFile, parent node_modules, etc.)
- when passing a string result must be equal or inside of this folder
v5.0.0-beta.6
Features
- add
restrictions
option, which allows to restrict the allowed paths to resolve too
Bugfixes
- add support for conditions in array for the
exports
field