rollbar 3.0.0-beta.5 → 3.0.0

package/.git-blame-ignore-revs

@@ -1,2 +1,4 @@
-# Prettier mass-format
+# 10/07/2025 | Format codebase with prettier, excluding examples (#1349)
 7a829f8ac3bbd146425a401b8434cf9cbaddaba1
+# 03/07/2024 | Integrate prettier to the project and ci and prettify project (#1133)
+443290f2a2f3bb7640cd3383dd95dea872773508

package/AGENTS.md

@@ -0,0 +1,21 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+Rollbar.js is the cross-platform SDK for Rollbar error monitoring. Browser runtime code sits in `src/browser/`, Node handlers in `src/server/`, React Native-specific modules in `src/react-native/`, and shared systems in `src/tracing/`, `src/telemetry.*`, and `src/utility/`. Public entry points flow through `src/rollbar.js` into bundled artifacts under `dist/` (do not edit generated files). Type definitions live in `index.d.ts`. Integration examples and docs are in `examples/` and `docs/`, while CLI helpers and release scripts live under `scripts/`. Tests mirror the source layout inside `test/`, with replay-focused coverage in `test/replay/`.
+
+## Build, Test, and Development Commands
+
+Use `npm run build` for production bundles and `npm run build:dev` during debugging. `npm test` executes both browser (Web Test Runner) and server (Mocha) suites; target subsets via `npm run test:wtr`, `npm run test:wtr:watch`, or `npm run test:server`. Lint with `npm run lint`, and rely on `npm run format` / `npm run format:check` for Prettier parity. Before publishing, run `npm run validate` to enforce ES5 compatibility and verify example snippets, then package distributables with `npm run pack`.
+
+## Coding Style & Naming Conventions
+
+This repo is an ES module project (`package.json` sets `"type": "module"`). ESLint rules in `eslint.config.js` enforce 2-space indentation, single quotes (via Prettier), `no-console` outside `scripts/`, maximum cyclomatic complexity of 35, and grouped alphabetized imports. The `unused-imports` plugin must leave files warning-free. Prefer PascalCase for exported classes or constructors, camelCase for functions and variables, and keep side-effect files named `<feature>.js` or `<feature>.cjs` to match existing patterns.
+
+## Testing Guidelines
+
+Author browser-facing specs under `test/browser.*.test.js` and Node scenarios under `test/server.*.test.js`. Session replay code should carry dedicated unit and integration coverage in `test/replay/**`. Tests use Mocha with Chai assertions and Sinon stubs. Add fixtures in `test/fixtures/` when mocking rrweb payloads or HTTP exchanges. Ensure `npm test` and `npm run validate:es5` succeed before opening a PR, especially after touching bundling or transport logic.
+
+## Commit & Pull Request Guidelines
+
+Follow the existing history by writing imperative, present-tense commit messages (e.g., `Add import linting guard (#1410)`). Each PR should summarize behavior changes, call out linked issues, and include test evidence or reproduction steps. Update relevant docs (`docs/`, `examples/`, `README.md`) for public-facing changes, avoid leaving TODOs, and surface any follow-up work in the PR description rather than the code. For security-sensitive fixes, coordinate disclosure via `SECURITY.md` instructions before merging.

package/CONTRIBUTING.md

@@ -1,112 +1,107 @@
 # Contributing to Rollbar.js
 
-Thank you for your interest in contributing to Rollbar.js! We welcome contributions from the community.
+Thanks for helping Rollbar.js! Whether you are polishing docs, reporting a bug, adding a framework example, or enhancing SDK features, your contribution matters. This SDK ships in mission-critical environments, so we lean on automation: tests, linting, formatting. That keeps changes low-risk while keeping the process open and welcoming. Jump in wherever you feel inspired and ask questions early and often.
 
-## Getting Started
+Rollbar.js is also AI-coding-agent ready: `AGENTS.md` documents Codex-specific guidelines and `CLAUDE.md` covers Claude’s conventions so automated assistants can operate safely alongside humans. Feel free to point AI tools at these docs when co-authoring patches.
 
-### Prerequisites
+## Ways to contribute
 
-- Node.js version 18 or higher
-- npm
+- Improve docs, READMEs, or examples to make Rollbar easier to adopt
+- Reproduce and fix bugs across browsers, Node, or React Native
+- Add tests, new features, or quality-of-life improvements
+- Share integration snippets, tutorials, or demo apps
 
-### Setup
+If you are unsure where to start, browse the GitHub issues page (<https://github.com/rollbar/rollbar.js/issues>) or open an issue/discussion, and maintainers can help scope a task that fits your interests.
 
-1. Fork the repository on GitHub
-2. Clone your fork locally:
+## Quick start
+
+**Prerequisites**
+
+- Node.js 18+ and npm 9+
+- A GitHub fork or branch you can push to
+
+**Setup**
+
+1. Fork the repository and clone your fork:
    ```bash
-   git clone https://github.com/your-username/rollbar.js.git
+   git clone https://github.com/<your-username>/rollbar.js.git
    cd rollbar.js
    ```
-3. Install dependencies:
+2. Install dependencies:
    ```bash
    npm install
    ```
-4. Build the project:
+3. (Optional) Verify the baseline:
    ```bash
-   npm run build
+   npm run build:dev
+   npm test
    ```
 
-## Development Workflow
+Keep branches focused on a single improvement. CI reruns the full suite on every push, so you can rely on it while iterating.
 
-### Running Tests
+## Local development workflow
 
-Run all tests:
+### Linting and autofixes
 
-```bash
-npm test
-```
+- `npm run lint` checks the entire repo with ESLint’s flat config.
+- `npm run lint:fix` runs ESLint with `--fix`. Run this before every commit so import ordering, unused variables, and other autofixable issues are taken care of automatically.
 
-Run only browser tests:
+### Formatting
 
-```bash
-npm run test-browser
-```
+- `npm run format` applies Prettier to JavaScript, configs, Markdown, JSON, and YAML. Run it before committing; it is safe to run repeatedly.
+- `npm run format:check` is the read-only version CI uses. Use it locally when you want to double-check a patch without mutating files.
 
-Run only server tests:
+### Tests
 
-```bash
-npm run test-server
-```
+- `npm test` runs both browser (`npm run test:wtr`) and server (`npm run test:server`) suites.
+- `npm run typecheck` runs the TypeScript pass (via `tsconfig.test.json`) so TS-based tests surface declaration mismatches early.
+- Scope runs as needed:
+  - `npm run test:wtr -- --watch` for browser tests with live reload.
+  - `npm run test:server test/server.my-feature.test.{js,ts}` to focus on one file.
+- `npm run validate` executes ES5 compatibility and example snippets. Use it when touching bundling, transports, or documentation code.
 
-### Code Style
+### Builds
 
-- We use ESLint for code quality. Run `npm run lint` before submitting
-- Code should follow the existing style patterns in the codebase
-- Use 2 spaces for indentation
-- Use single quotes for strings
+- `npm run build:dev` compiles bundles in development mode (faster debug cycle).
+- `npm run build` + `npm run postbuild` mirrors the release pipeline; only run this when you need to inspect distributables.
 
-### Making Changes
+## Code style philosophy
 
-1. Create a feature branch from `master`:
+- Prettier defines whitespace, quotes, and wrapping. Never hand-format files.
+- ESLint (with `unused-imports`, `no-console`, etc.) enforces correctness. Let the tools win; rerun `npm run lint:fix && npm run format` if your editor disagrees.
+- Prefer small, incremental commits that respect the SDK’s ES module architecture and multi-platform outputs. Automation keeps everyone aligned, so let the tools guide you instead of enforcing personal style.
 
-   ```bash
-   git checkout -b my-feature-name
-   ```
+## Pull request checklist
 
-2. Make your changes and ensure:
-   - All tests pass
-   - Code follows our style guidelines
-   - New features include appropriate tests
-   - Documentation is updated if needed
-   - Examples are updated if needed
+Before opening or updating a PR:
 
-3. Commit your changes with a clear message:
-   ```bash
-   git commit -m "Add feature: description of what you added"
-   ```
-
-## Submitting a Pull Request
-
-1. Push your changes to your fork:
-
-   ```bash
-   git push origin my-feature-name
-   ```
+- `npm run lint:fix` and `npm run format`
+- `npm test` (plus any focused suites you touched)
+- `npm run validate` when build outputs, transports, or examples change
+- Update docs (`README.md`, `docs/`, `examples/`) for user-facing behavior
+- Document risk, testing evidence, and follow-ups in the PR description
+- Reference related issues and describe the user benefit in plain language
 
-2. Open a pull request on GitHub against the `master` branch
+CI re-runs lint (`--max-warnings 0`), `format:check`, tests, and ES5/example validation on every push, so if something slips through locally it will be caught automatically, and there is no need to stress.
 
-3. In your pull request description:
-   - Clearly describe what changes you've made
-   - Reference any related issues
-   - Include testing steps if applicable
+## Troubleshooting linting & formatting
 
-4. Wait for review and address any feedback
+- **ESLint cannot find a plugin**: run `npm install` to ensure devDependencies are installed; the flat config loads plugins via native `import`, so Node 18+ is required.
+- **`unused-imports` keeps flagging helper params**: delete the import or prefix intentional unused params with `_` (e.g., `_req`) and rerun `npm run lint:fix`.
+- **Prettier rewrites the entire file**: confirm you are using the repo’s pinned Prettier version (`npm run format` handles it) or format just the file you touched (`npm run format -- src/foo.js`).
+- **CI fails `format:check` but local format looks fine**: make sure your editor isn’t stripping trailing newlines or converting line endings; set `git config core.autocrlf false` (Unix) or `true` (Windows) and format again.
+- **`eslint` reports “Parsing error: Cannot find module”**: ensure every import has a `.js` extension because Rollbar.js is pure ESM, and missing extensions break the parser.
 
-## Reporting Issues
+Still stuck? Open a draft PR, start a GitHub Discussion, or tag maintainers in an issue; we’re happy to help.
 
-- Use GitHub Issues to report bugs
-- Include as much detail as possible:
-  - Steps to reproduce
-  - Expected behavior
-  - Actual behavior
-  - Environment details (browser, Node.js version, etc.)
+## Continuous integration expectations
 
-## Questions?
+GitHub Actions runs lint, `format:check`, browser/server tests, ES5 validation, and documentation snippet checks on every PR. Hooks are optional; CI is the enforcer so you can iterate locally without fear. Keep patches scoped, trust the automation, and explain what you validated in your PR body.
 
-If you have questions, please:
+## Need help?
 
-- Check existing issues and documentation
-- Open a GitHub issue for clarification
-- Email support@rollbar.com for urgent matters
+- Start a GitHub Discussion or issue for questions and feature ideas.
+- For security-sensitive findings, follow `SECURITY.md`.
+- Unsure where to contribute? Browse open GitHub issues or start a discussion describing what excites you, and maintainers will help scope the work.
 
-Thank you for contributing to Rollbar.js!
+Thanks again for partnering with us to improve Rollbar.js!

package/babel.config.json

@@ -12,6 +12,13 @@
           "ie": "11"
         }
       }
+    ],
+    [
+      "@babel/preset-typescript",
+      {
+        "allowDeclareFields": true,
+        "onlyRemoveTypeImports": true
+      }
     ]
   ]
 }

package/bower.json

@@ -18,7 +18,7 @@
     "Makefile",
     "travis.yml",
     "package.json",
-    "webpack.config.cjs",
+    "webpack.config.js",
     "browserstack*"
   ]
 }

package/dist/plugins/jquery.min.js

@@ -1 +1 @@
-!function(){"use strict";!function(r,n,t){var e=n.Rollbar;if(e){e.configure({payload:{notifier:{plugins:{jquery:{version:"0.0.8"}}}}});var a=function(r){if(e.error(r),n.console){var t="[reported to Rollbar]";e.options&&!e.options.enabled&&(t="[Rollbar not enabled]"),n.console.log(r.message+" "+t)}};r(t).ajaxError((function(r,n,t,a){var o=n.status,i=t.url,u=t.type;if(o){var s={status:o,url:i,type:u,isAjax:!0,data:t.data,jqXHR_responseText:n.responseText,jqXHR_statusText:n.statusText},d=a||"jQuery ajax error for "+u;e.warning(d,s)}}));var o=r.fn.ready;r.fn.ready=function(r){return o.call(this,(function(n){try{r(n)}catch(r){a(r)}}))};var i=r.event.add;r.event.add=function(n,t,e,o,u){var s,d=function(r){return function(){try{return r.apply(this,arguments)}catch(r){a(r)}}};return e.handler?(s=e.handler,e.handler=d(e.handler)):(s=e,e=d(e)),s.guid?e.guid=s.guid:e.guid=s.guid=r.guid++,i.call(this,n,t,e,o,u)}}}(jQuery,window,document)}();
+!function(){"use strict";!function(r,n,t){var e=n.Rollbar;if(e){e.configure({payload:{notifier:{plugins:{jquery:{version:"0.0.8"}}}}});var a=function(r){if(e.error(r),n.console){var t="[reported to Rollbar]";e.options&&!e.options.enabled&&(t="[Rollbar not enabled]"),n.console.log(r.message+" "+t)}};r(t).ajaxError(function(r,n,t,a){var o=n.status,i=t.url,u=t.type;if(o){var s={status:o,url:i,type:u,isAjax:!0,data:t.data,jqXHR_responseText:n.responseText,jqXHR_statusText:n.statusText},d=a||"jQuery ajax error for "+u;e.warning(d,s)}});var o=r.fn.ready;r.fn.ready=function(r){return o.call(this,function(n){try{r(n)}catch(r){a(r)}})};var i=r.event.add;r.event.add=function(n,t,e,o,u){var s,d=function(r){return function(){try{return r.apply(this,arguments)}catch(r){a(r)}}};return e.handler?(s=e.handler,e.handler=d(e.handler)):(s=e,e=d(e)),s.guid?e.guid=s.guid:e.guid=s.guid=r.guid++,i.call(this,n,t,e,o,u)}}}(jQuery,window,document)}();