Fix resolving packages that use the package exports feature
#452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ferdinand Thiessen <rpm@fthiessen.de>
skjnldsv
approved these changes
Jan 31, 2023
|
Wanna release v8.2.1 ? |
I would highly appreciate that :) |
|
appreciate you doing the release or me? xD |
|
You, I do not think I have the permission level for creating release^^ |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Required for packages that make use of the
exportsfeatures, as theeslint-plugin-importrelays onbrowserify/resolvefor resolving packages which does not support theexportsfeature (supported by Node 12.7+).(usage example: import the
gettextmodule from thel10npackage)