NodeJS/Browser Agent

2026 Release Notes

Version
Date
Changes

6.2.19

May 27. 2026

Resolved Issues:

  • Fixed a browser agent issue where coverage was not reported for dynamically loaded JavaScript files in applications using on-demand module loading.

6.2.15

May 13, 2026

Resolved Issues:

  • Fixed an issue where files with URL-scheme paths were not properly excluded during build scanning.

  • Improved path handling for Windows environments during the scanning process.

6.2.12

May 5, 2026

New Features and Updates:

  • Extended all test runners to include group context in execution completion reporting.

Resolved Issues:

  • Fixed build-scanning issues that could result in missing server-side coverage for certain bundled application setups.

  • Improved source path resolution to correctly handle non-standard path formats encountered during scanning.

6.2.8

Apr 27, 2026

New Features and Updates:

  • Updated the Mocha executor to use direct API calls for execution lifecycle management.

Resolved Issues:

  • Fixed a module initialization issue causing unintended side effects on import.

6.2.6

Apr 9, 2026

Resolved Issues:

  • Addressed several CLI configuration inconsistencies introduced in a prior release.

  • Improved error handling for unexpected server responses during agent initialization.

6.2.1

Mar 30, 2026

New Features and Updates:

  • Standardized CLI parameter names to align with other SeaLights agents: --branchName, --buildName, --failOnError, --scanDir, --scmType, --excludeFiles, --moduleName, --repositoryUrl, --disableTia, --file, and --filesFolder.

  • Added command aliases for improved usability:

    • completeScan

    • openTestStage / startTestStage

    • closeTestStage / endTestStage

  • Maintained full backward compatibility by preserving all existing parameter and command names as aliases.

  • Allowed all agent parameters to be overridden via the SeaLights backend. Track overrides with cockpit messages and debug logs for visibility, ensuring parity with other agents.

  • Refactored CLI and configuration system. Maintained full compatibility with existing scripts and integrations.

Resolved Issues:

  • Addressed an issue where the default excludedFiles glob pattern (e.g., test/**/*) matched a file instead of a directory, causing fs.statSync to throw ENOTDIR. Now safely skips unresolvable paths.

6.1.1163

Mar 9, 2026

New Features and Updates:

  • Updated engines field in package.json to >= Node 16.x.

6.1.1162

Mar 3, 2026

New Features and Updates:

  • Added default .slignore.instrument for various frontend frameworks.

6.1.1160

Feb 24, 2026

Resolved Issues:

  • Bumped sl-request to 1.0.8 and overrode ajv to 8.18.0 to resolve a high-severity vulnerability.

6.1.1159

Feb 16, 2026

Resolved Issues:

  • Updated dependencies to use newer version of qs (latest: 6.14.1) to remove Snyk-reported vulnerability.

6.1.1158

Feb 16, 2026

Resolved Issues:

  • Prevented CockpitNotifier errors from appearing in the console.

6.1.1154

Feb 10, 2026

New Features and Updates:

  • --excludeSourceMapFiles now allows skipping copying of source map files to instrumentation output and optionally deleting them from the workspace directory. Previously worked only for .js.map files; now also works for .css.map.

6.1.1153

Feb 5, 2026

Resolved Issues:

  • Fixed failure to embed sl-mapping for pure JavaScript files (without source maps). Previously, this caused coverage to not appear.

6.1.1152

Feb 4, 2026

New Features and Updates:

  • Added a cache-busting mechanism when using a preamble file. Cached deployment files containing an outdated buildSessionId are now automatically synchronized when a new buildSessionId is detected in the preamble file.

6.1.1151

Feb 3, 2026

New Features and Updates:

  • Added console messages across all relevant slnodejs commands, including the Mocha test runner.

  • Added a console message for the existing validation that checks whether a build already exists for the specified buildSessionId.

  • Moved selected lifecycle logs to the info level to avoid duplication with console output.

6.1.1150

Jan 27, 2026

New Features and Updates:

  • Added support for the prId parameter in the Mocha executor.

  • Introduced an API to manually load executions in the remote-agent.

  • Introduced an API to manually set TIA status in the remote-agent.

6.1.1147

Jan 13, 2026

Resolved Issues:

  • Removed obsolete Footprints v5 code from the agent.

6.1.1143

Jan 13, 2026

New Features and Updates:

  • Added support for running the remote-agent with compressed sl-mapping files.

2025 Release Notes

Version
Date
Changes

6.1.1142

Dec 17, 2025

New Features and Updates:

  • Added a public method to allow the remote-agent to send the Agent Started event.

6.1.1140

Dec 17, 2025

New Features and Updates:

  • Added an isRunning flag to the remote-agent to prevent redundant start or stop calls when the agent state has not changed.

6.1.1133

Dec 5, 2025

New Features and Updates:

  • Added a warning message in both the console and the Cockpit when a scan detects the same methods being scanned more than once.

  • Included executionId in all relevant HTTP requests, both in root headers and request metadata.

  • Updated the Mocha executor and nycReport to skip loading the default buildSessionId file when labId is provided.

  • Aligned Mocha behavior to continue supporting the default buildSessionId file only when labId is not provided.

Last updated

Was this helpful?