-
Notifications
You must be signed in to change notification settings - Fork 509
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
feat: resolve actual subpaths before guessing #527
Conversation
Codecov Report
@@ Coverage Diff @@
## main #527 +/- ##
==========================================
- Coverage 76.50% 76.48% -0.03%
==========================================
Files 73 73
Lines 7594 7578 -16
Branches 755 750 -5
==========================================
- Hits 5810 5796 -14
+ Misses 1783 1781 -2
Partials 1 1
|
If you like this approach we can also extract into a |
A refactor to mlly would be nice idea for reverse resolving subpaths ππΌ |
ee6ea64
to
3f8ced5
Compare
@danielroe is this ready to review ? |
It is. |
@danielroe Had to create a new branch to fix the conflicts. You can force push from there #1395 |
I don't believe there are any conflicts in this branch. I resolved them 5 days ago with a rebase. |
Ah yes ignore me π€¦ GitHub UI fooled me |
π Linked issue
β Type of change
π Description
This resolves actual subpaths rather than guessing, so (for example)
node-fetch-native/dist/polyfill.mjs
can correctly be resolved tonode-fetch-native/polyfill
and back again.π Checklist