Browser Logger

​

Installation

npm install @squasher/browser-logger

mkdir -p public/vendor
cp node_modules/@squasher/browser-logger/dist/browser-logger.umd.js public/vendor/browser-logger.umd.js

<script src="/vendor/browser-logger.umd.js"></script>
<script>
  window.SquasherBrowserLogger.init({
    apiKey: "sq_pk_your_key",
    projectId: "your-project-id"
  });
</script>

​

Configuration

import { initBrowserLogger } from "@squasher/browser-logger";

const browserLogger = initBrowserLogger({
  apiKey: "sq_pk_your_key",
  projectId: "your-project-id",
  endpoint: "https://ingest.squasher.ai",
  captureConsoleErrors: true,
});

export default browserLogger;

​

Usage Example

import { initBrowserLogger } from "@squasher/browser-logger";

const browserLogger = initBrowserLogger({
  apiKey: "sq_pk_your_key",
  projectId: "your-project-id",
});

console.error("Checkout failed", new Error("Card declined"), { cartId: "cart_123" });

void browserLogger.flush();

• sdk.name = "@squasher/browser-logger"
• The current page URL
• The browser user agent
• Serialized console arguments in extra.console_arguments

​

Privacy/Security Considerations

• The browser logger captures every argument passed to console.error(). Do not log secrets, access tokens, card data, or raw personal data in browser console calls.
• The current page URL is attached to each event. Avoid placing sensitive values in query strings or route params if those pages initialize the logger.
• Initialize the logger only in environments where client-side error forwarding is expected, such as production or staging builds.
• Use HTTPS for the page and the ingest endpoint so the project key and payload are encrypted in transit.

​

Agent handoff

Use @squasher/browser-logger only when the app needs lightweight console.error capture without the full browser SDK. Keep the project key browser-safe, avoid logging secrets, and verify with one console.error call.