fix: fix issues with native node fetch

[arunanshub]

This is an attempt to fix the issue highlighted in nuxt/nuxt#19245 and nuxt/nuxt#19245/issuecomment-1575671354.

[codecov]

Codecov Report

Merging #245 (0f4249d) into main (5524f8a) will increase coverage by 0.06%.
The diff coverage is 100.00%.

❗ Current head 0f4249d differs from pull request most recent head 22c30be. Consider uploading reports for the commit 22c30be to get more accurate results

@@            Coverage Diff             @@
##             main     #245      +/-   ##
==========================================
+ Coverage   86.50%   86.57%   +0.06%     
==========================================
  Files           5        5              
  Lines         415      417       +2     
  Branches       61       62       +1     
==========================================
+ Hits          359      361       +2     
  Misses         56       56              

Impacted Files	Coverage Δ
src/fetch.ts	89.31% <100.00%> (+0.09%)	⬆️

[pi0]

Thanks!

[171h]

I saw where the PR code was modified in Files changed, I remember this issue antfu/vitesse-nuxt3, the issue error is still exists when I update with nuxi upgrage -f and the ofetch has update to v1.1.0.
I hope the information I provide can provide assistance for possible future repairs.

---

• Operating System: Windows_NT
• Node Version: v20.1.0
• Nuxt Version: 3.5.3
• Nitro Version: 2.4.1
• Package Manager: unknown
• Builder: vite
• User Config: modules, css, devtools
• Runtime Modules: @unocss/nuxt@0.51.13, @pinia/nuxt@0.4.11, @nuxthq/ui@2.3.0, @element-plus/nuxt@1.0.5
• Build Modules: -

---

 ERROR  Failed to fetch web fonts                                                                                                                            23:15:36  


 ERROR  fetch failed (https://fonts.googleapis.com/css2?family=DM+Sans&family=DM+Serif+Display&family=DM+Mono&display=swap)                                  23:15:36  

  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async Module.$fetch2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:239:15)

[arunanshub]

@171h I'm using Node v20 too, but it somehow works on my machine. Have you tried deleting node_modules, .nuxt, .output folders?

On the other hand, I personally don't like the recursive implementation of $fetchRaw and onError functions.

Edit: I am unable to replicate the error in Windows 11.

[171h]

I have deleted node_modules, .nuxt, .output.
This error exist on Node v20 and v19, but v16 will be ok. So I still use v16 in the past few months due to the issue.

[171h]

I used nvm to manage the nodejs version. I just upgraded nvm to the latest version 1.11.1 and then reinstalled nodejs. Amazingly, this error disappeared on node v20.3.0, but still exists on v19.9.0.

[171h]

This problem may already have been fixed by this pr nodejs/node#47732 since node v20.2.0