feat: quick TTFB & TTI for large content

[SgtPooki]

Title

feat: quick TTFB & TTI for large content

Description

This updates helia-service-worker-gateway to @helia/verified-fetch@1.3.0 and ensures we're respecting the request event's AbortSignal.

Summary of changes (thanks @2color):

1. Handle aborts from original fetch event
2. Don't await Cache API puts
3. Respect cache-control: no-cache & pragma: no-cache

Notes & open questions

after getting #122 and ipfs/helia-verified-fetch#26 merged.. then updating @helia/verified-fetch in service-worker-gateway locally…. large video loading feels much more responsive

For the below, I hardcoded my local kubo node to ensure trustless-gateway.link was not being used.

big-buck-bunny TTFB/TTI for the code in this PR from kubo node with content:

Brave: consistently < 800ms
FireFox: 159ms

1. A local kubo gateway configured (that has the content) npx kubo daemon
2. cache disabled in the browser.

You can use the below process and code snippet to get TTFB:

1. clear out service worker
2. reload the page (you will see redirect page, make sure config is set up properly)
3. click "load content" or reload.
4. When the video renders, pause it.
5. Run the below snippet in the dev console

new PerformanceObserver((entryList) => {
  const videoLoadEntries = performance.getEntriesByType('navigation')
    .filter((entry) => entry.name.includes('bafybeidsp6fva53dexzjycntiucts57ftecajcn5omzfgjx57pqfy3kwbq.ipfs.helia-sw-gateway.localhost'))

  for (const videoLoadEntry of videoLoadEntries) {
    console.log(`TTFB: ${videoLoadEntry.duration}ms for ${videoLoadEntry.name}`)
  }
}).observe({
  type: 'navigation',
  buffered: true
});

big-buck-bunny TTFB/TTI for code in this PR pulling from fresh kubo node:

Brave: 4-12s.

see #131 (comment)

big-buck-bunny TTFB/TTI for main branch code on kubo node with content

In Brave: Consistently over 1000ms.. with a fresh service worker

In Firefox: idk why but it was returning within a few ms.. old cache/sw that wouldn't go away? https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox didn't always take

big-buck-bunny TTFB/TTI for code in main from fresh kubo node:

Brave: averaging ~70-90 seconds

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b064d20) to head (da12865).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #138   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           35        35           
  Branches         5         5           
=========================================
  Hits            35        35           

Flag	Coverage Δ
node	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SgtPooki]

self review

[SgtPooki]

changes deployed on https://bafybeidsp6fva53dexzjycntiucts57ftecajcn5omzfgjx57pqfy3kwbq.ipfs.sw.sgtpooki.com/

use https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox to clear data on firefox.

TTFB on firefox from sw.sgtpooki.com is ~14000ms

[2color]

Barring a bunch of nits this is great!

Summary of changes (for me):

1. Handle aborts from original fetch event
2. Don't await Cache API puts (TIL)
3. Respect cache-control: no-cache

(Don't cache 206s was already there but new to my eyes)