Registry / observability / fundebug-javascript

fundebug-javascript

library2.8.8jsnpmunverified

Fundebug-javascript is a client-side library designed for real-time error monitoring of JavaScript applications, enabling developers to quickly detect and diagnose issues impacting user experience. The current stable version is 2.8.8, last published in March 2023. While its core functionality has been stable, updates have historically addressed browser compatibility, added new features like performance metrics, and improved TypeScript support. Key differentiators include automatic capture of various frontend errors (JavaScript execution, resource loading, HTTP requests), support for Source Map restoration, recording of user behavior (clicks, HTTP requests, page navigation, console logs), and a 'screen recording' feature to visually re-create error scenarios, aiding rapid debugging and issue reproduction. It's primarily used for web and frontend applications, with companion libraries for specific frameworks like Vue.js and environments like WeChat Mini Programs.

observability

npm install fundebug-javascript

package ↗homepage ↗

INSTALL

IMPORT

SIG · FUNDEBUG-JAVASCRIP

fundebug-javascript

observabilityjavascriptv2.8.8

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

fundebug

✓ import * as fundebug from 'fundebug-javascript';

✗ const fundebug = require('fundebug-javascript');

While CommonJS `require` works, ESM `import * as` is the recommended pattern, especially since v2.0.0 which added comprehensive TypeScript support. The library exports a default object containing its methods.

fundebug.init

✓ fundebug.init({ apikey: 'YOUR_APIKEY' });

✗ fundebug.apikey = 'YOUR_APIKEY';

Since v2.0.0, `fundebug.init()` is the recommended and TypeScript-friendly method for configuration, including setting the API key. Direct assignment to `fundebug.apikey` might still work but is less robust and not type-safe.

FundebugEvent

✓ import type { FundebugEvent } from 'fundebug-javascript';

The package ships with TypeScript types. For type-only imports, use `import type` to avoid bundling unnecessary runtime code, adhering to modern TypeScript practices. This is useful for defining custom error event structures or handlers.

This quickstart demonstrates how to initialize Fundebug with an API key and custom metadata, simulate both uncaught and caught errors, and highlight optional data collection settings.

import * as fundebug from 'fundebug-javascript'; const FUNDEBUG_API_KEY = process.env.FUNDEBUG_API_KEY ?? ''; // Initialize Fundebug with your API key and other optional configurations fundebug.init({ apikey: FUNDEBUG_API_KEY, metaData: { // Example of custom metadata user: { id: 'user-123', name: 'John Doe' }, appVersion: '1.0.0' }, // Opt-in to monitor HTTP request bodies for detailed debugging monitorHttpBody: true, // Introduced in v2.8.4 // To silently ignore performance data on errors silentPerformance: false // Introduced in v1.5.0 }); console.log('Fundebug initialized. Try triggering an error...'); // Simulate a JavaScript error document.addEventListener('DOMContentLoaded', () => { const btn = document.createElement('button'); btn.textContent = 'Trigger Error'; document.body.appendChild(btn); btn.onclick = () => { throw new Error('This is a simulated error from Fundebug quickstart!'); }; }); // Manually report an error try { // Some risky operation const data: any = null; data.property.doSomething(); } catch (error: any) { fundebug.notifyError(error, { customInfo: 'Caught error in try-catch block' }); }

Debug

Known issues

breakingVersion 2.0.0 introduced `fundebug.init()` as the primary configuration method, providing better type safety and extensibility. While direct property assignments (e.g., `fundebug.apikey = '...'`) might still function in CommonJS environments, migrating to `fundebug.init()` is crucial for full TypeScript compatibility and recommended for all new projects and upgrades.

fix

Replace direct property assignments with calls to `fundebug.init({ apikey: 'YOUR_APIKEY', ...otherOptions })`.

affects: >=2.0.0

gotchaFundebug-javascript is designed for browser-side error monitoring. Embedding your API key directly in client-side code exposes it publicly. Consider using environment variables during build time or a backend proxy to securely manage and inject the API key, especially in production environments.

fix

Use environment variables for the API key (e.g., `process.env.FUNDEBUG_API_KEY`) and ensure they are securely managed by your build process or server configuration.

affects: >=1.0.0

gotchaError monitoring tools, including Fundebug, can collect sensitive user data from error contexts. Features like `setHttpBody` (v1.3.0) and `monitorHttpBody`/`monitorHttpResponse` (v2.8.4) can capture HTTP request/response bodies, which may contain personally identifiable information (PII) or other sensitive data. These options are typically opt-in.

fix

Carefully review Fundebug's configuration options and data collection policies. Ensure that options collecting sensitive data (e.g., `monitorHttpBody`) are only enabled when necessary and in compliance with privacy regulations (GDPR, CCPA) and your organization's policies.

affects: >=1.3.0

gotchaMixing CommonJS `require()` and ES Modules `import` in the same project, especially for packages that primarily target one module system, can lead to interoperability issues (e.g., `ERR_REQUIRE_ESM`). Although `fundebug-javascript` has types and can be imported as ESM, its original README shows `require`, suggesting a CommonJS primary export.

fix

Ensure consistent module usage (either all ESM or all CJS) across your project. If you must mix, use dynamic `import()` in CJS for ESM modules, or use `import * as` for CJS modules in an ESM context, and ensure your bundler (Webpack, Rollup, Vite) is configured for dual-mode support if applicable.

affects: >=1.0.0

Errors

Common errors & fixes

ReferenceError: fundebug is not defined

The Fundebug library was not imported or initialized correctly before being used, often due to incorrect module syntax (e.g., `require` in an ESM context or vice-versa) or script loading order.

fix

Ensure you are using the correct import statement for your module system (e.g., `import * as fundebug from 'fundebug-javascript';` for ESM) and that the script is loaded before any calls to `fundebug` functions. For older browsers, ensure the CDN script tag is placed appropriately.

TypeError: fundebug.init is not a function

You are attempting to use the `fundebug.init()` method, but either an older version of the library (pre-2.0.0) is loaded, or the `fundebug` object you're accessing doesn't have the `init` method due to incorrect import or bundling.

fix

Upgrade `fundebug-javascript` to version 2.0.0 or higher. Verify your import statement: `import * as fundebug from 'fundebug-javascript';` is recommended. If using a CDN, ensure you're referencing a modern version of the script.

Fundebug: api key is not configured.

The Fundebug API key was not provided or was provided incorrectly during initialization, preventing the library from sending error reports to your Fundebug project.

fix

Call `fundebug.init({ apikey: 'YOUR_APIKEY' })` with a valid API key obtained from your Fundebug account. Ensure the key is a string and that there are no typos.

Upgrade

Version history

2.8.8latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

27 hits · last 30 days

node

OpenAI (training)

Resources

packagehttps://www.npmjs.com/package/fundebug-javascript ↗

homepagehttps://www.fundebug.com ↗