bpkeepmeajdffneiimcknfnjodekcgnh
Turn all your developer console logs into alerts. Every log message in frontend and backend code is turned into a friendly popup on the webpage. Done with console.log, console.info, console.debug, console.warn, console.error, and console.trace in the browser along with the equivalent on the server. The popup contains the message and also the stack trace to the message. Clicking the stack trace opens up the file in a separate browser tab. Server side logging supports all languages. v2.0.2 - Bug fix for overlapping logs. v2.0.1 - Bug fix for not displaying logs on YouTube. v2.0.0 - Change log displays, add better handling of displaying source code, create stacked logs option, and add log limit option. v1.1.1 - Display the name, message, and stack of errors as collapsible objects. v1.0.1 - Revert back to older version. Issue with implementing OAuth 2.0. v0.6.0 - Add URL whitelist to determine which domains to display console.log, console.info, console.debug, console.warn, console.error, and console.trace messages on. v0.5.2 - Bug fix for server side log toggle switch working after service worker goes idle. v0.5.1 - Bug fix for server side log toggle switch not working. v0.5.0 - Add the ability to view server side logs in the browser as popups. This includes all languages (Node, Java, Python, etc.). v0.4.0 - Add ability to position the developer logs from console.log, console.info, console.debug, console.warn, console.error, and console.trace calls. v0.3.0 - Add ability to set the size of the developer logs from console.log, console.info, console.debug, console.warn, console.error, and console.trace calls. v0.2.3 - Fix bug where enable/disable toggle switch doesn't work after navigating pages. - Handle fetch API call failures when analyzing stack traces from console.log, console.info, console.debug, console.warn, console.error, and console.trace calls. v0.2.2 - Fix bug where console.log, console.info, console.debug, console.warn, console.error, and console.trace messages are missed when the service worker is inactive. v0.2.1 - Fix bug of initial values for opacity and timer being 0. - Make console.log, console.info, console.debug, console.warn, console.error, and console.trace enabled on install. v0.2.0 - Add slider to adjust how long the popups appear for. - Add slider to adjust the opacity of the popups. - Replace setTimeout call with extension messaging API. v0.1.1 - Make the extension initially enabled when installed. v0.0.2 - Change the overflow of the popup title so the icons don't disappear. v0.0.1 - Make console.log, console.info, console.debug, console.warn, and console.error appear as popups.
Copy Console
Copy console logs with specific patterns Supercharge your debugging workflow by instantly capturing and copying console logs with pattern matching! Feel free to contact if you present issues V1.4 - Add configurable whitelist to copy console.logs only in sites from the list - Default whitelist: localhost, bolt.new, lovable.dev
Network & Console Logger
Records network requests and console logs from web pages. Easily capture and download network requests and console logs from any website. Perfect for developers, QA testers, and anyone who needs to debug web applications. ✨ KEY FEATURES: - Capture network requests (API calls) with full request/response details - Log all console messages (log, warn, error, info) - Filter by specific domains (UI URL and API URL) - Download logs as formatted text files - Request/Response body capture - Headers and status information - Duration tracking for each request - Clean and intuitive interface 🎯 PERFECT FOR: - Frontend developers debugging API calls - QA testers capturing bug reports - DevOps monitoring application behavior - Anyone needing to export console logs 🔒 PRIVACY: - All data stays local - nothing is uploaded to external servers - Only captures from domains you specify - Toggle logging on/off anytime 📝 HOW TO USE: 1. Click the extension icon 2. Enter your API URL and UI URL 3. Toggle logging ON 4. Save settings and refresh your page 5. Use your application normally 6. Click "Download Logs" to export
ConsoleSpy
Console to Cursor MCP bridges your browser's console with Cursor IDE. It allows you to easily feed console logs back into the Cursor Composer interface for a more seamless development experience. • Send all console logs (info, warnings, errors) to your local MCP server • Access browser console logs directly in Cursor's AI Composer • Ask Cursor's AI to analyze and debug console errors • Maintain a persistent log history for your debugging sessions • Works with localhost and development environments Perfect for developers who use Cursor IDE and want to leverage AI for debugging web applications. Simply install the extension, run the companion MCP server (available on GitHub), and start debugging with Cursor's AI assistant. This extension is open source and requires the companion MCP server to function. Visit our GitHub repository for setup instructions and documentation.
Error Tracker
Track and report errors on web pages with detailed information and screenshots # Error Tracker Chrome Extension Error Tracker is designed to automatically detect and report web page errors, providing developers and QA teams with comprehensive error tracking capabilities. The extension captures JavaScript errors, network errors, and console errors, along with optional screenshots, to help identify and resolve issues efficiently. - **Automatic Error Detection** - JavaScript errors - Network errors (4xx, 5xx) - Console errors and warnings - UI/DOM errors - Unhandled promise rejections - **Visual Error Tracking** - Automatic screenshot capture on error (optional) - Visual context for debugging - Reduced screenshot size for better performance 1. Download from Chrome Web Store (link coming soon) 2. Click "Add to Chrome" 3. Configure domains and permissions as needed 1. **Initial Setup** - Click the extension icon - Configure allowed domains - Set up error tracking preferences 2. **Error Tracking** - Errors are automatically captured - View errors in the extension popup - Filter and sort as needed - Export error reports if required - Uses html2canvas for screenshots - Local storage for data persistence - MutationObserver for UI error tracking - Network request monitoring - Console override for error capture To modify or enhance the extension: 1. Clone the repository 2. Make changes to the source files 3. Load unpacked extension in Chrome 4. Test your changes 5. Submit pull request if contributing extension/ ├── manifest.json # Extension configuration ├── background.js # Background service worker ├── content.js # Content script for error tracking ├── popup.html # Extension popup interface ├── popup.js # Popup functionality └── lib/ # External libraries └── html2canvas.min.js ``` 1. Fork the repository 2. Create a feature branch 3. Commit your changes 4. Push to the branch 5. Create a Pull Request MIT License - feel free to use and modify as needed. For issues or feature requests: - Create an issue in the repository - Contact: [Your Email] - GitHub: [Your GitHub Repository] Essential for core extension functionality to: - Monitor and detect errors across web pages - Capture error details from different domains - Enable error tracking on user-specified websites Access is limited to error detection only and does not collect personal or sensitive data. Required for accurate error tracking: - Identify which tab generated an error - Associate errors with correct page contexts - Enable proper error reporting across multiple tabs Only collects minimal tab information necessary for error tracking functionality. Required to capture errors and take screenshots only when the user actively interacts with the extension. This permission is essential for: - Capturing error context in the active tab - Taking screenshots when errors occur (if enabled) - Accessing page content for error details The permission is only activated when users interact with the extension, ensuring minimal access to user data. The extension uses html2canvas.min.js, which is: - Bundled locally within the extension - Never loaded from external sources - Used only for capturing error screenshots - Runs entirely in the user's browser No external code is loaded or executed. Critical for network error detection: - Monitor HTTP error responses (4xx, 5xx) - Track failed network requests - Capture network error details Only activated during error situations and does not monitor successful requests. Necessary for maintaining extension functionality: - Store user preferences and settings - Cache error logs locally for 24 hours - Save domain whitelist configuration All data is stored locally on the user's device and is automatically deleted after 24 hours.
