mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
* chore: move posthog-rrweb into the monorepo Imports the posthog-rrweb fork (currently published as v0.0.60) into packages/rrweb/ so that the rrweb packages release from this repo via the existing changesets pipeline. This collapses the current two-step publish flow (posthog-rrweb -> npm -> posthog-js) into a single monorepo release. Scope of the move: - Snapshot taken from posthog-rrweb@main; rrvideo, rrweb-player and web-extension are intentionally dropped because we do not consume them from posthog-js. - The seven packages we publish today continue to publish from this repo: @posthog/rrweb, @posthog/rrweb-types, @posthog/rrweb-utils, @posthog/rrdom, @posthog/rrweb-snapshot, @posthog/rrweb-record and @posthog/rrweb-plugin-console-record. - Internal-only packages (rrdom-nodejs, @posthog/rrweb-replay, @posthog/rrweb-all, @posthog/rrweb-packer, the experimental plugins) are listed under changesets ignore. - packages/browser now depends on @posthog/rrweb-record, @posthog/rrweb-plugin-console-record and @posthog/rrweb-types via workspace:* instead of pinned npm versions. Tooling/config updates: - pnpm-workspace.yaml gains packages/rrweb/* and packages/rrweb/plugins/* globs and a small catalog for vite, vite-plugin-dts and esbuild-plugin-umd-wrapper. - turbo.json picks up vite.config.* as build inputs and adds prepublish / check-types tasks used by the rrweb subpackages. - Root devDependencies hoist esbuild, esbuild-plugin-umd-wrapper and rollup-plugin-visualizer so vite builds resolve correctly. - .npmrc adds a few trust-policy-exclude entries for transitive deps brought in by the rrweb tree that lost provenance attestations. - release.yml extends the publish matrix to the seven publishable rrweb packages. - library-ci.yml adds an rrweb job (vitest + puppeteer under xvfb) that only runs when packages/rrweb/** changes. No runtime behavior changes are intended: the recorder bundle in packages/browser is byte-identical to main (verified locally), and the published rrweb packages get a single patch bump via the accompanying changeset. * stop using rrweb npm package and point imports to local rrweb * fix tests * fix tests * fix docker build * fix docker build * silence false positives * fix for tue's comment * pin package version * add minimal permissions to silence alert
46 lines
1.2 KiB
HTML
46 lines
1.2 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
<title>Document</title>
|
|
<script>
|
|
// monkey patches .childNodes to make them unaccessible
|
|
// emulates the effect of some frameworks, specifically salesforce lightning-ui
|
|
Object.defineProperty(Element.prototype, 'childNodes', {
|
|
get() {
|
|
throw new Error('childNodes was hijacked by framework');
|
|
},
|
|
});
|
|
|
|
Object.defineProperty(Node.prototype, 'childNodes', {
|
|
get() {
|
|
throw new Error('childNodes was hijacked by framework');
|
|
},
|
|
});
|
|
|
|
Node.prototype.contains = function () {
|
|
throw new Error('contains was hijacked by framework');
|
|
};
|
|
|
|
Node.prototype.getRootNode = function () {
|
|
throw new Error('getRootNode was hijacked by framework');
|
|
};
|
|
|
|
MutationObserver = class {
|
|
constructor() {
|
|
throw new Error('MutationObserver was hijacked by framework');
|
|
}
|
|
};
|
|
</script>
|
|
</head>
|
|
<body>
|
|
<ul>
|
|
<li>a</li>
|
|
<li>b</li>
|
|
<li>c</li>
|
|
<li>d</li>
|
|
</ul>
|
|
</body>
|
|
</html>
|