Investigate whether to replace jest-chrome with @webext-core/fake-browser.
Context:
jest-chrome has had no releases since 2020 and does not track the modern MV3 API surface
@webext-core/fake-browser is an in-memory implementation of the WebExtension API (not just a mock), actively maintained by the WXT author
Potential benefits:
- Tests for
src/lib/config.ts could exercise real storage.sync behavior (set → get round-trip, onChanged listeners) instead of asserting on hand-rolled mock returns
- Works with both Jest and Vitest, so a switch can land independently of any test-runner migration
Decide whether the upside is worth the migration effort, then act.
Investigate whether to replace
jest-chromewith@webext-core/fake-browser.Context:
jest-chromehas had no releases since 2020 and does not track the modern MV3 API surface@webext-core/fake-browseris an in-memory implementation of the WebExtension API (not just a mock), actively maintained by the WXT authorPotential benefits:
src/lib/config.tscould exercise realstorage.syncbehavior (set → get round-trip,onChangedlisteners) instead of asserting on hand-rolled mock returnsDecide whether the upside is worth the migration effort, then act.