fix(yup): fix Yup wrong import statement assuming default export #427
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
|
🎉 This PR is included in version 2.9.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Hi,
Yup was imported with a default import but in the original library no default export is defined. This is only working at the moment when building the lib because of the tsconfig option
esModuleInterop.I believe this is causing an issue only in specific scenarios (I had the issue while using a Webpack 4 setup with an older ts-loader version) but since it's a tiny change, might be reasonable to fix.
This is the error you could eventually see and this PR resolve:
TS1192: Module '"/node_modules/@hookform/resolvers/yup/src/yup"' has no default export.