An in-page HTTP controller for frontend development to intercept, modify, and simulate API responses directly in the browser.
PocketMocker is an in-page HTTP controller for frontend development that intercepts, modifies, and simulates API responses directly in the browser. It provides a visual control panel to override HTTP responses, helping developers build and test UIs faster without backend dependencies or separate mock servers.
Frontend developers and teams who need to mock API responses during development, test edge cases, and debug network requests without leaving the browser.
Developers choose PocketMocker for its browser-integrated visual control panel, smart mock data generation, and seamless integration with tools like Vite, enabling instant UI updates and efficient team collaboration without complex setup.
In-page HTTP controller for frontend development. Intercept, modify, and simulate API responses directly in the browser.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The floating panel allows direct manipulation of HTTP responses without switching tools, enabling instant UI updates as mentioned in the 'Debug Instantly' section.
Template syntax like @guid and @name generates realistic test data efficiently, reducing manual mock creation as shown in the Smart Mock Data Generation examples.
Supports path parameters and wildcards for complex API routes, making it easy to mock dynamic endpoints as detailed in the URL Pattern Matching section.
Vite plugin saves mock rules to config files, facilitating sharing across teams, which is highlighted in the Team Collaboration Mode.
Relies on monkey patching fetch and XMLHttpRequest, so it may not intercept all network requests, such as those from libraries that bypass standard APIs, and is ineffective in non-browser environments.
Dynamic response functions use plain JavaScript without built-in TypeScript types for request parameters, which could lead to errors in typed codebases.
Designed exclusively for development, so it cannot be used for production mocking or in testing environments outside of dev, as indicated by the NODE_ENV check.