fix: add target pathname currectly

[jonasolesen]

🔗 Linked issue

#5

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Sets the correct target path by using the pathname property on the URL object as described in the linked issue. While the static type of the target object from which I got the pathname is any, it was in fact an URL object during my limited runtime debugging. However, I don't know if this is always the case, so feel free to correct me or come up with a more complete solution 🙂

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #6 (0e79f05) into main (1ed43da) will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   65.00%   64.98%   -0.03%     
==========================================
  Files           8        8              
  Lines        1046     1048       +2     
  Branches       73       73              
==========================================
+ Hits          680      681       +1     
- Misses        365      366       +1     
  Partials        1        1              

Files Changed	Coverage Δ
src/_utils.ts	77.29% <66.66%> (-0.22%)	⬇️

[pi0]

Thank you for the quick PR ❤️

This regression comes from legacy codebase refactors to URL parser. I have added pathname || path to to be sure about not introducing unwanted breaking changes.

Also added tests to make sure behavior remains as desired.