ghosttrap-cli 0.3.23__tar.gz → 0.3.25__tar.gz

{ghosttrap_cli-0.3.23 → ghosttrap_cli-0.3.25}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ghosttrap-cli
-Version: 0.3.23
+Version: 0.3.25
 Summary: Watch for errors streaming from ghosttrap.io
 Project-URL: Homepage, https://github.com/alex-rowley/ghosttrap-cli
 Requires-Python: >=3.10

{ghosttrap_cli-0.3.23 → ghosttrap_cli-0.3.25}/ghosttrap_cli/cli.py

@@ -27,7 +27,7 @@ def _harden_signals():
         except (OSError, ValueError):
             pass
 
-__version__ = "0.3.23"
+__version__ = "0.3.25"
 
 GHOSTTRAP_SERVER = "wss://ghosttrap.io/stream/"
 CONFIG_DIR = os.path.expanduser("~/.ghosttrap")
@@ -75,13 +75,17 @@ Read `~/.ghosttrap/config.json` for state. It contains:
 
 1. Detect the current repo from `git config --get remote.origin.url` (returns `owner/name`).
 2. Find a matching entry in config by looking for one whose `owner`/`name` equals the detected slug. If no match, tell the user to run `ghosttrap setup`. (The owner/name on a config entry auto-refreshes from the server when the repo is renamed or transferred, so always match against the entry's stored owner/name, not the config key.)
-3. If `sdk_installed` is false or missing: install the SDK (`pip install ghosttrap-sdk`), wire `ghosttrap.init("<token>")` into the app startup. For Django projects, also add `"ghosttrap.django.GhostTrapApp"` to INSTALLED_APPS (re-attaches logging handler after Django's dictConfig) and `"ghosttrap.django.GhostTrapMiddleware"` to MIDDLEWARE (catches unhandled view exceptions). The SDK auto-hooks into Celery task_failure if Celery is installed, and attaches a logging handler for logger.exception() calls. Use whatever pattern the project already uses for configuration (env vars, settings files, hardcoded — match the existing style). Then update the config: set `sdk_installed: true`, `sdk_version`, `init_file` to record what you did. Only pass `send_user=True` to `init()` if the user explicitly asks for user context in reports — it's PII and stays off by default.
+3. If `sdk_installed` is false or missing: install the SDK (`pip install ghosttrap-sdk`), wire `ghosttrap.init("<token>")` into the app startup. For Django projects, also add `"ghosttrap.django.GhostTrapApp"` to INSTALLED_APPS (re-attaches logging handler after Django's dictConfig) and `"ghosttrap.django.GhostTrapMiddleware"` to MIDDLEWARE (catches unhandled view exceptions). The SDK auto-hooks into Celery task_failure if Celery is installed, catches unhandled exceptions in background threads (threading.excepthook), and attaches a logging handler for logger.exception() calls. Bare `logger.error(...)` calls with no exception are NOT reported unless the user explicitly asks — then pass `trap_logs=True` to `init()` (sdk >= 0.4.7); warn them that chatty codebases will flood. Use whatever pattern the project already uses for configuration (env vars, settings files, hardcoded — match the existing style). Then update the config: set `sdk_installed: true`, `sdk_version`, `init_file` to record what you did. Only pass `send_user=True` to `init()` if the user explicitly asks for user context in reports — it's PII and stays off by default.
 4. Run `ghosttrap peek --clear` with `run_in_background: true`. The `--clear` flag skips any stale backlog from prior sessions so you only get fresh errors.
 
 ## Manual capture
 
 For caught exceptions or non-exception conditions the user explicitly wants reported, use `ghosttrap.trap(exc_or_message)` from app code — pass an exception instance or a string. Synthetic string events arrive as type `TrappedEvent` with the caller's stack. Only wire this in when the user asks for it; don't add `trap()` calls speculatively.
 
+## Browser errors
+
+If the user wants browser-side JavaScript errors captured (often described as "console errors that never reach ghosttrap"), the SDK's Django integration ships a same-origin relay (ghosttrap-sdk >= 0.4.6). Wire it in only when asked: add `path("ghosttrap/", include("ghosttrap.django.urls"))` to the root URLconf and `<script src="{% static 'ghosttrap/ghosttrap.js' %}" defer></script>` to the base template. Browser events then arrive like any other error — JS error type, page URL in the traceback header, JS stack as frames (minified if the app's bundles are; there is no source-map support).
+
 ## When peek returns
 
 1. **Immediately restart peek** in the background before doing anything else — this ensures you're listening for the next error while you work on the current one. Use plain `ghosttrap peek` here (no `--clear`) — you only want to skip backlog at session start.

{ghosttrap_cli-0.3.23 → ghosttrap_cli-0.3.25}/ghosttrap_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ghosttrap-cli
-Version: 0.3.23
+Version: 0.3.25
 Summary: Watch for errors streaming from ghosttrap.io
 Project-URL: Homepage, https://github.com/alex-rowley/ghosttrap-cli
 Requires-Python: >=3.10

{ghosttrap_cli-0.3.23 → ghosttrap_cli-0.3.25}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ghosttrap-cli"
-version = "0.3.23"
+version = "0.3.25"
 description = "Watch for errors streaming from ghosttrap.io"
 readme = "README.md"
 requires-python = ">=3.10"