feat: sync Rokt kit with upstream 1.30.1 — page-view capture as page_events

[rmi22186]

Summary

Ports the Rokt kit changes shipped upstream in mparticle-javascript-integration-rokt since the monorepo's 1.28.3 snapshot (PR #1300), bringing kits/rokt up to v1.30.1:

• v1.29.0 — feat: prevent caching of active_time_on_site_ms attribute (#106): adds active_time_on_site_ms to the selectPlacements attribute-persistence deny list so it is forwarded on the current call but never cached and re-sent stale.
• v1.30.0 — feat: capture page views and surface as page_events in selectPlacements (#109): captures PageView events into kit-owned localStorage (query params stripped, capped at 25, cleared on session end and when noTargeting is set) and sends them as a JSON page_events attribute on selectPlacements.
• v1.30.1 — refactor: rename timeOnPage to activeTimeOnPage in selectPlacements page_events (#110).

Files changed

• src/Rokt-Kit.ts, src/selectPlacementsAttributePersistence.ts, test/src/tests.spec.ts, CHANGELOG.md — taken wholesale from upstream main (no upstream changes conflicted with monorepo adaptations).
• package.json / package-lock.json — version bump 1.28.3 → 1.30.1 only.
• vite.config.ts — adds test.execArgv: ['--no-experimental-webstorage'] (see below).

Preserved monorepo adaptations

• package.json: repository URL, @mparticle/web-sdk in peerDependencies (^3.0.0) + devDependencies (^2.73.1), semantic-release devDependencies removed.
• vite.config.ts: @mparticle/web-sdk kept external in builds, process.env.PACKAGE_VERSION define, test aliases to monorepo internal types and dist/mparticle.common.js.
• tsconfig.json: baseUrl/paths mapping for @mparticle/web-sdk/internal.

New: Node >= 25 test-environment fix

The new upstream page-view tests rely on window.localStorage. On Node >= 25, Node's experimental webstorage defines a localStorage global that is undefined without --localstorage-file, and its presence makes Vitest's jsdom environment skip installing jsdom's working implementation — 18 tests fail (upstream has the same failure locally on Node 26; its CI pins Node 24, while this repo's kit-test CI job uses node-version: latest). Fixed by passing --no-experimental-webstorage to the Vitest workers via test.execArgv so jsdom's Storage is used on any Node version.

Test plan

• npm ci in kits/rokt — clean install from the committed lock file
• npm run build — iife/cjs/esm bundles + d.ts build successfully
• npm test — 228/228 tests pass on Node 26.5.0 (CI-like latest) and Node 24.19.0 (upstream-pinned)

[cursor]

PR Summary

Medium Risk
Changes what behavioral data is sent to Rokt on selectPlacements and uses browser localStorage for page history; privacy/opt-out paths (noTargeting, session clear) are implemented but partners should verify expectations.

Overview
Brings kits/rokt from 1.28.3 to 1.30.1 (upstream Rokt integration).

Page views → Rokt placements: On PageView events (when targeting is enabled), the kit persists a bounded history in localStorage (mpPageViews, max 25, query strings stripped via sanitizeUrl). selectPlacements adds a JSON page_events attribute built from that store, including derived activeTimeOnPage from consecutive activeTimeOnSite values. History is cleared on session end, on init when noTargeting is set, and capture is skipped entirely when targeting is disabled. Page-view handling runs in process() even if the launcher is not ready yet.

Attribute caching: active_time_on_site_ms is added to the selectPlacements persistence deny list so it is sent on the current call but not cached for later placements.

Tests / tooling: Large Vitest coverage for page-view behavior and deny-list behavior; vite.config.ts passes --no-experimental-webstorage to Vitest workers so window.localStorage works under Node 25+ with jsdom.

^{Reviewed by Cursor Bugbot for commit d11687e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud