fix: export domhandler' Element from it's exports field #565
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the motivation for this pull request?
Fix error when running with webpack build
bug fix
What is the current behavior?
Got Module Not Found error
Package path ./lib/node is not exported from package ..../node_modules/domhandler
I found the related issue #252 (comment) and pr #296 , which exports the
Element
type ofdomhandler
.But
domhandler
has usedexports
field, only exports index files https://github.com/fb55/domhandler/blob/master/package.json#L13What is the new behavior?
Require
Element
directly from 'domhandler' index.Error no longer appears and webpack build runs correctly
Checklist: