2.2: run scrapes from the service worker and store them in IndexedDB by EnesYilmazcode · Pull Request #8 · EnesYilmazcode/AmazonSellerScraper

Add a message catalog and a typed router for the service worker

EnesYilmazcode

committed

cb5b19d

Add an IndexedDB store for runs, products, pages, lastValues and the outbox

EnesYilmazcode

committed

24f2b00

Give the run record states from idle to done and a reason for how it ended

EnesYilmazcode

committed

90d5036

Run scrapes from a service worker engine that owns the run and its data

EnesYilmazcode

committed

c6b38ab

Move run data out of storage.local into IndexedDB as schema 4

EnesYilmazcode

committed

077e61c

Answer every worker message through the router and wire in the engine

EnesYilmazcode

committed

ec83596

Make the scraper parse only and report pages to the worker

EnesYilmazcode

committed

c3b18fc

Send spread results to the worker instead of writing storage from the page

EnesYilmazcode

committed

5caeaf7

Render the popup from the worker's state and start and stop through it

EnesYilmazcode

committed

cb63631

Ship messages.js to pages, drop unused content globals, bump to 2.2.0

EnesYilmazcode

committed

a2c26a3

Tell extension pages from content scripts by URL, since a popup can open in a tab

EnesYilmazcode

committed

0cc1f7e

Open the database again when another context closes it, and end the run if it cannot

EnesYilmazcode

committed

01b58b3

Show how a run ended even when its database cannot be opened

EnesYilmazcode

committed

14a2528

Read run state from session storage and IndexedDB in the Chromium harness

EnesYilmazcode

committed

51329a7

Upgrade harness: expect 2.2.0 and schema 4, and cut a 2.1 run off mid-scrape

EnesYilmazcode

committed

2029a6f

Keep the specs and tests of checked-out older builds out of the test runs

EnesYilmazcode

committed

0dfb3a9

Chromium harness: a run tab taken elsewhere ends the run and stays where it went

EnesYilmazcode

committed

be49263

Document the service worker run engine, IndexedDB storage and schema 4

EnesYilmazcode

committed

7fde97c

End a run cut off by an update as updated, not interrupted

EnesYilmazcode

committed

7502721

Ask a page again when it has not reported 20 seconds after the worker opened it

EnesYilmazcode

committed

f9b9b73

End a run whose tab left Amazon while its next page was loading

EnesYilmazcode

committed

433a794

Report a page again when the worker re-asks after every try failed

EnesYilmazcode

committed

95e0204

Let the install defaults land before the page cap test sets its own

EnesYilmazcode

committed

b96d1fa

End runs left live only in IndexedDB, keep the newest 10 runs, and order the 3 to 4 migration

EnesYilmazcode

committed

e2f5ad4

Read the run-tab and 503 scenarios through the 2.2 run record

EnesYilmazcode

committed

7ce2963

Navigation Menu

Repository navigation

2.2: run scrapes from the service worker and store them in IndexedDB - #8

2.2: run scrapes from the service worker and store them in IndexedDB#8
EnesYilmazcode wants to merge 25 commits into
rebuild/p2-v2.1from
rebuild/p3-run-engine

Commits on Sep 25, 2026

Add a message catalog and a typed router for the service worker

Add an IndexedDB store for runs, products, pages, lastValues and the outbox

Give the run record states from idle to done and a reason for how it ended

Run scrapes from a service worker engine that owns the run and its data

Move run data out of storage.local into IndexedDB as schema 4

Answer every worker message through the router and wire in the engine

Make the scraper parse only and report pages to the worker

Send spread results to the worker instead of writing storage from the page

Render the popup from the worker's state and start and stop through it

Ship messages.js to pages, drop unused content globals, bump to 2.2.0

Tell extension pages from content scripts by URL, since a popup can open in a tab

Open the database again when another context closes it, and end the run if it cannot

Show how a run ended even when its database cannot be opened

Read run state from session storage and IndexedDB in the Chromium harness

Upgrade harness: expect 2.2.0 and schema 4, and cut a 2.1 run off mid-scrape

Keep the specs and tests of checked-out older builds out of the test runs

Chromium harness: a run tab taken elsewhere ends the run and stays where it went

Document the service worker run engine, IndexedDB storage and schema 4

End a run cut off by an update as updated, not interrupted

Ask a page again when it has not reported 20 seconds after the worker opened it

End a run whose tab left Amazon while its next page was loading

Report a page again when the worker re-asks after every try failed

Let the install defaults land before the page cap test sets its own

End runs left live only in IndexedDB, keep the newest 10 runs, and order the 3 to 4 migration

Read the run-tab and 503 scenarios through the 2.2 run record