-
Notifications
You must be signed in to change notification settings - Fork 28
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
fix: Fallback to parentLoad
if parsing fails
#104
Conversation
I added a test that shows how this works around #105 but this PR should help with a lot of scenarios and edge cases and makes |
The tests ran on my own fork but show this failing on node v16 due to the expected rejection in Looking at that test, I would expect this to fail on every Node version with my changes. I guess it's only failing on that version due to how |
$ git log --oneline --no-decorate v1.8.0..HEAD a3497a9 v1.8.1 88605a7 fix: Fallback to `parentLoad` if parsing fails (#104) 1c6f7b0 fix: Explicitly named exports should be exported over `export *` (#103) 29f51f6 fix: CommonJs bare specifier resolution (#96) a8b39f7 fix: `parentResolve` is not a function (#100) c87090d fix: Named export `Hook` missing from types (#92)
Closes #101