fix: surface 'cause' for undici network errors

[nikhilgupta345]

Resolves #641

---

Before the change?

Network errors from undici are presented with "fetch failed" without showing the underlying cause that undici also presents.

After the change?

Network errors now correctly propagate the 'cause' from undici

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

• Yes
• No

---

[gr2m]

great PR, thank you!!! It looks like coverage dropped, could you please have a look?

------------------------|---------|----------|---------|---------|-------------------
File                    | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
------------------------|---------|----------|---------|---------|-------------------
All files               |     100 |    97.82 |     100 |     100 |                   
 fetch-wrapper.ts       |     100 |    97.67 |     100 |     100 | 144               
 get-buffer-response.ts |     100 |      100 |     100 |     100 |                   
 index.ts               |     100 |      100 |     100 |     100 |                   
 version.ts             |     100 |      100 |     100 |     100 |                   
 with-defaults.ts       |     100 |      100 |     100 |     100 |                   
------------------------|---------|----------|---------|---------|-------------------
Jest: "global" coverage threshold for branches (100%) not met: 97.82%

[nikhilgupta345]

great PR, thank you!!! It looks like coverage dropped, could you please have a look?

------------------------|---------|----------|---------|---------|-------------------
File                    | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
------------------------|---------|----------|---------|---------|-------------------
All files               |     100 |    97.82 |     100 |     100 |                   
 fetch-wrapper.ts       |     100 |    97.67 |     100 |     100 | 144               
 get-buffer-response.ts |     100 |      100 |     100 |     100 |                   
 index.ts               |     100 |      100 |     100 |     100 |                   
 version.ts             |     100 |      100 |     100 |     100 |                   
 with-defaults.ts       |     100 |      100 |     100 |     100 |                   
------------------------|---------|----------|---------|---------|-------------------
Jest: "global" coverage threshold for branches (100%) not met: 97.82%

Unfortunately I'm not sure what's going on because the test wouldn't pass unless line 144 was being executed. I also confirmed by putting console.logs immediately before and after line 144 and ensured they were both executed during the test suite. Any ideas?

[gr2m]

The line is covered but not all branches (possible execution paths) are. I think it's ok to ignore the line from coverage. I'm out on mobile right now, I forgot the syntax for jest coverage

[nikhilgupta345]

The line is covered but not all branches (possible execution paths) are. I think it's ok to ignore the line from coverage. I'm out on mobile right now, I forgot the syntax for jest coverage

Aha just figured that out at the same time. Just pushed up a fix. Thanks!

[github-actions]

🎉 This PR is included in version 8.1.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀