New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More →
@grafana/faro-instrumentation-performance-timeline
Advanced tools
@grafana/faro-instrumentation-performance-timeline - npm Package Versions
Changelog
1.2.5
- Feat: New session tracking capabilities (optional, disabled by default) where users can choose to use tracked or volatile sessions (#374).
Changelog
1.2.4
- Breaking: The sdk meta now only contains the version number of Faro. This is to reduce beacon payload size. If users need the full data including all integrations, it can be added as outlined in the docs.(#370)
- Feature: new experimental session manager which can be configured to use persistent or volatile sessions (#359).
- Fix: user provided session attributes were not sent (#372).
Changelog
1.2.3
- Fix: Disable keepalive in web-sdk fetch transport when the payload length is over 60_000 (#353).
- Fix: Add 'isK6Browser' field to k6 meta object (#361).
Changelog
1.2.0 - 1.2.2
- Feat: Detect if Faro is running inside K6 browser to distinguish between lab and field data (#263).
- Feat: Enable users to configure per-error boundary
pushErrorbehavior. - Deps: Upgrade project to use the current Node LTS version (lts/hydrogen, v18)
- Deps: Dependency updates
- Deps: CVE-2023-45133 - Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
Changelog
1.2.0 - 1.2.2
- Feat: Detect if Faro is running inside K6 browser to distinguish between lab and field data (#263).
- Feat: Enable users to configure per-error boundary
pushErrorbehavior. - Deps: Upgrade project to use the current Node LTS version (lts/hydrogen, v18)
- Deps: Dependency updates
- Deps: CVE-2023-45133 - Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
Changelog
1.1.3
- Fix: Update opentelemetry packages used by the Web-Tracing-Instrumentation to address CVE-2023-38704 (#242)