1 item
Mock fetch, XHR, async ID, and Firestore flows on the current page without opening DevTools. JediMock lets frontend developers and QA engineers mock API behavior directly on the page they are testing. Activate a quick JSON response from the popup, activate any complete saved mock with one click, or open Advanced setup for managing named mocks, response merging, request-body modification, fallback behavior, response headers, per-call rules, async ID flows, Firebase v8 Firestore fields, cURL import, sharing, and configuration import/export. JediMock works locally in your browser. It has no backend, analytics, advertising, or permanent website access. An active mock can be stopped from the extension, with JediMock.stop(), by reloading, or by navigating away. The popup includes an optional, user-initiated button to support JediMock on Buy Me a Coffee. A dismissible reminder may occasionally appear after a successful activation. Supporting the developer is not required and does not unlock or change any functionality. Key capabilities: • Match fetch and XMLHttpRequest calls by method and URL. • Use Contains, Exact, or single-segment Pattern matching. • Return JSON with a chosen status and delay. • Merge a real JSON response or modify an outgoing JSON request. • Add request and response headers. • Configure network fallback and per-call response rules. • Mock async ID and Firebase v8 Firestore flows. • Import cURL and import, export, or share local configurations. • Save, rename, load, duplicate, and delete named mock configurations locally.
Aug 28, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.