npm - @osdk/react-components - Versions diffs - 0.19.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb → 0.19.0 - Mend

@osdk/react-components 0.19.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb → 0.19.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (112) hide show

package/docs/CSSVariables.md CHANGED Viewed

@@ -1508,17 +1508,13 @@ For more comprehensive theming, override the Blueprint tokens that the OSDK toke
 ## Dark Mode
-`@osdk/react-components` ships built-in dark-theme overrides. They activate automatically in any of three ways:
+`@osdk/react-components` ships built-in dark-theme overrides that activate when `[data-bp-color-scheme="dark"]` is set on an ancestor element (typically `<html>`) — matching Blueprint's own convention so the OSDK + Blueprint tokens flip together. The supported way to set the attribute is `<OsdkThemeProvider>` from `@osdk/react-components/experimental/theme`; see [OsdkThemeProvider](./OsdkThemeProvider.md) for the full reference, including `defaultTheme="system"` (the default, follows `prefers-color-scheme`), runtime toggles via `useOsdkTheme`, and controlled mode for integrating with an external theme store.
-1. **`prefers-color-scheme: dark`** — matches the [Foundry custom widgets dark theme guidance](https://www.palantir.com/docs/foundry/custom-widgets/dark-theme). When a parent application (Foundry, the OS) declares dark color scheme, the widget switches without any host configuration.
-2. **`[data-bp-color-scheme="dark"]` or `.bp6-dark`** — matches the Blueprint convention. Set this attribute / class on any ancestor (often `<html>`) to force dark explicitly. Useful when the OS preference doesn't reflect what the host wants, or when previewing dark mode in isolation.
-3. **`[data-theme="dark"]`** — matches the Tailwind/Primer/Storybook toolbar convention. Lets Storybook (and other hosts that already use this attribute) opt into dark without duplicating overrides.
-The attribute paths win over the media query when both apply, giving hosts an explicit override. Under `[data-bp-color-scheme="dark"]` / `.bp6-dark`, Blueprint flips `--bp-*` itself, so `dark.css` only re-maps `--osdk-*` tokens. The other two selectors also flip the relevant `--bp-*` tokens because Blueprint doesn't fire there.
+Under `[data-bp-color-scheme="dark"]` Blueprint flips its own `--bp-*` tokens, so `dark.css` only re-maps the subset of `--osdk-*` tokens that have no `--bp-*` counterpart or that intentionally diverge from Blueprint's value.
 ### Adding your own dark overrides
-To customize dark-mode tokens beyond the defaults, declare your overrides in a higher layer using the same selectors:
+To customize dark-mode tokens beyond the defaults, declare your overrides in a higher layer using the same selector:
 ```css
 @layer osdk.styles, user.theme;
@@ -1526,15 +1522,7 @@ To customize dark-mode tokens beyond the defaults, declare your overrides in a h
 @import "@osdk/react-components/styles.css" layer(osdk.styles);
 @layer user.theme {
-  @media (prefers-color-scheme: dark) {
-    :root {
-      --osdk-background-primary: #0a0a0a;
-      --osdk-table-row-bg-alternate: #161616;
-    }
-  }
-  [data-bp-color-scheme="dark"],
-  .bp6-dark {
+  [data-bp-color-scheme="dark"] {
     --osdk-background-primary: #0a0a0a;
     --osdk-table-row-bg-alternate: #161616;
   }

package/docs/OsdkThemeProvider.md ADDED Viewed

@@ -0,0 +1,239 @@
+# OsdkThemeProvider
+Provides OSDK theme state to descendants and writes a `data-bp-color-scheme` attribute onto the document so the OSDK + Blueprint design tokens activate the right theme. Components inside the provider re-render automatically when the resolved theme changes.
+## Prerequisites
+Before using `OsdkThemeProvider`, complete the library setup described in [Prerequisites](./Prerequisites.md), in particular the CSS layer imports - the provider only flips an attribute; the OSDK token CSS does the rest.
+## Table of Contents
+- [Import](#import)
+- [Quick start](#quick-start)
+- [Props reference](#props-reference)
+- [`useOsdkTheme` hook](#useosdktheme-hook)
+- [Examples](#examples)
+  - [Default: follow the OS preference](#default-follow-the-os-preference)
+  - [Force light or dark with `defaultTheme`](#force-light-or-dark-with-defaulttheme)
+  - [Build a `ThemeToggle`](#build-a-themetoggle)
+  - [Drive the theme from an external store (controlled mode)](#drive-the-theme-from-an-external-store-controlled-mode)
+  - [Scope theming to a subtree](#scope-theming-to-a-subtree)
+- [Branching on the resolved theme in JS](#branching-on-the-resolved-theme-in-js)
+## Import
+```tsx
+import {
+  type OsdkThemeMode,
+  OsdkThemeProvider,
+  type ResolvedOsdkTheme,
+  useOsdkTheme,
+} from "@osdk/react-components/experimental/theme";
+```
+## Quick start
+```tsx
+import { OsdkThemeProvider } from "@osdk/react-components/experimental/theme";
+function App() {
+  return (
+    <OsdkProvider client={client}>
+      <OsdkThemeProvider>
+        {/* your app */}
+      </OsdkThemeProvider>
+    </OsdkProvider>
+  );
+}
+```
+With no props the provider follows `prefers-color-scheme` and re-renders when the OS preference changes. To override the OS at runtime, descendants call `setTheme` from [`useOsdkTheme`](#useosdktheme-hook).
+> **Always render the provider somewhere above OSDK components.** OSDK components stay in light mode without it — the CSS only flips when `data-bp-color-scheme="dark"` is on an ancestor, and the provider is the supported way to manage that attribute. If an external store already owns your theme value, use [controlled mode](#drive-the-theme-from-an-external-store-controlled-mode) instead of skipping the provider — that way descendants can still call `useOsdkTheme`.
+## Props reference
+| Prop             | Type                                          | Default                    | Description                                                                                                                                                                                                                                                                                             |
+| ---------------- | --------------------------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `theme`          | `"light" \| "dark" \| "system"` _(optional)_  | —                          | Controlled theme. When provided, the provider does not maintain its own state — the parent must respond to `onThemeChanged` (or update its own external store) and re-render with the new value. See [Drive the theme from an external store](#drive-the-theme-from-an-external-store-controlled-mode). |
+| `defaultTheme`   | `"light" \| "dark" \| "system"`               | `"system"`                 | Initial theme when uncontrolled. Ignored when `theme` is provided. The provider owns the state from then on; descendants change it at runtime via `useOsdkTheme().setTheme`.                                                                                                                            |
+| `onThemeChanged` | `(theme: OsdkThemeMode) => void` _(optional)_ | —                          | Fires whenever a descendant calls `setTheme`. Use this to layer side effects (persistence, analytics) on top of the default state update, or to drive an external store in controlled mode.                                                                                                             |
+| `target`         | `HTMLElement \| null` _(optional)_            | `document.documentElement` | Element to write `data-bp-color-scheme` onto. Defaults to `<html>` so Blueprint portals (popovers, dialogs, tooltips) — which render outside the React tree — also receive the theme. See [Scope theming to a subtree](#scope-theming-to-a-subtree).                                                    |
+| `children`       | `React.ReactNode`                             | —                          | Subtree that should resolve the theme via `useOsdkTheme`.                                                                                                                                                                                                                                               |
+### `defaultTheme` modes
+| Mode       | Behavior                                                                                |
+| ---------- | --------------------------------------------------------------------------------------- |
+| `"system"` | Follows the OS `prefers-color-scheme` setting and re-renders when it changes (default). |
+| `"light"`  | Starts in light mode regardless of the OS preference.                                   |
+| `"dark"`   | Starts in dark mode regardless of the OS preference.                                    |
+`"system"` is the only mode where the resolved theme can change without anyone calling `setTheme` — it reacts to the OS preference flipping while your app is open.
+## `useOsdkTheme` hook
+```tsx
+const { theme, resolvedTheme, setTheme } = useOsdkTheme();
+```
+| Field           | Type                            | Description                                                                                               |
+| --------------- | ------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| `theme`         | `"light" \| "dark" \| "system"` | The requested mode, including `"system"`.                                                                 |
+| `resolvedTheme` | `"light" \| "dark"`             | The concrete theme actually applied to the DOM. When `theme === "system"`, tracks `prefers-color-scheme`. |
+| `setTheme`      | `(next: OsdkThemeMode) => void` | Switch the requested mode at runtime.                                                                     |
+Must be called from a descendant of `<OsdkThemeProvider>`; throws otherwise.
+## Examples
+### Default: follow the OS preference
+The simplest setup — no props needed. The provider starts in `"system"` mode, listens to `prefers-color-scheme`, and flips automatically when the user toggles their OS appearance.
+```tsx
+import { OsdkThemeProvider } from "@osdk/react-components/experimental/theme";
+export function Root() {
+  return (
+    <OsdkProvider client={client}>
+      <OsdkThemeProvider>
+        <App />
+      </OsdkThemeProvider>
+    </OsdkProvider>
+  );
+}
+```
+To verify this in development, open Chrome DevTools → `⌘⇧P` → "Show Rendering" → set "Emulate CSS media feature prefers-color-scheme" to `light` or `dark`.
+### Force light or dark with `defaultTheme`
+Pin the initial mode if your app intentionally ships in light or dark regardless of the OS:
+```tsx
+<OsdkThemeProvider defaultTheme="dark">
+  <App />
+</OsdkThemeProvider>;
+```
+Users can still switch at runtime via `useOsdkTheme().setTheme`; `defaultTheme` only seeds the initial value.
+### Build a `ThemeToggle`
+A typical settings-bar control that lets the user pick light/dark/system:
+```tsx
+import {
+  type OsdkThemeMode,
+  useOsdkTheme,
+} from "@osdk/react-components/experimental/theme";
+const MODES: readonly OsdkThemeMode[] = ["light", "dark", "system"];
+export function ThemeToggle() {
+  const { theme, resolvedTheme, setTheme } = useOsdkTheme();
+  return (
+    <div role="group" aria-label="Theme">
+      {MODES.map((mode) => (
+        <button
+          key={mode}
+          type="button"
+          onClick={() => setTheme(mode)}
+          aria-pressed={theme === mode}
+        >
+          {mode}
+        </button>
+      ))}
+      {theme === "system" && (
+        <span aria-live="polite">(resolved: {resolvedTheme})</span>
+      )}
+    </div>
+  );
+}
+```
+Render it anywhere inside the provider:
+```tsx
+<OsdkThemeProvider>
+  <Header>
+    <ThemeToggle />
+  </Header>
+  <main>{/* ... */}</main>
+</OsdkThemeProvider>;
+```
+### Drive the theme from an external store (controlled mode)
+If the theme value already lives outside the OSDK tree (e.g. in a parent design-system provider), pass it in via the `theme` prop. The provider stops owning state; you re-render it with the new value when the store changes, and the provider rewrites `data-bp-color-scheme` accordingly.
+```tsx
+import {
+  type OsdkThemeMode,
+  OsdkThemeProvider,
+} from "@osdk/react-components/experimental/theme";
+import { useAppTheme } from "../store/theme.js"; // your own store hook
+export function AppRoot() {
+  // `theme` is owned by the app's store, not by the provider.
+  const theme = useAppTheme();
+  return (
+    <OsdkProvider client={client}>
+      <OsdkThemeProvider theme={theme}>
+        <App />
+      </OsdkThemeProvider>
+    </OsdkProvider>
+  );
+}
+```
+If descendants call `setTheme` from `useOsdkTheme()`, controlled mode does **not** update the provider's state — it fires `onThemeChanged` so you can route the change back into your store.
+```tsx
+<OsdkThemeProvider
+  theme={theme}
+  onThemeChanged={(next) => dispatch(setTheme(next))}
+>
+  <App />
+</OsdkThemeProvider>;
+```
+Use controlled mode whenever an external source of truth exists. Use uncontrolled (just `defaultTheme`) when the provider can own the state itself.
+### Scope theming to a subtree
+By default the provider writes `data-bp-color-scheme` onto `<html>` so portaled overlays (popovers, dialogs, tooltips) inherit the theme. To theme only a slice of the page — for example, embedding an OSDK dashboard inside a host app that already manages its own theme — pass a `target`:
+```tsx
+import { useRef } from "react";
+export function DashboardEmbed() {
+  const scopeRef = useRef<HTMLDivElement>(null);
+  return (
+    <div ref={scopeRef}>
+      <OsdkThemeProvider target={scopeRef.current} defaultTheme="dark">
+        <Dashboard />
+      </OsdkThemeProvider>
+    </div>
+  );
+}
+```
+Trade-off: portals from `@base-ui/react` / Blueprint render in a portal container that is **not** a descendant of `scopeRef`, so dropdowns and tooltips opened from inside the scoped subtree will follow the document-level theme, not the scoped one. Use the default (`<html>`) target unless you specifically need per-region theming.
+## Branching on the resolved theme in JS
+If you need to swap an asset or change a non-CSS value based on theme, read `resolvedTheme` — not `theme` — so the `"system"` mode resolves to a concrete `"light"` or `"dark"` for you:
+```tsx
+function LogoMark() {
+  const { resolvedTheme } = useOsdkTheme();
+  return (
+    <img
+      src={resolvedTheme === "dark" ? "/logo-dark.svg" : "/logo-light.svg"}
+      alt="Logo"
+    />
+  );
+}
+```

package/docs/Prerequisites.md CHANGED Viewed

@@ -124,6 +124,29 @@ All components resolve their visual properties through CSS custom properties. Th
 Per-component references list the `--osdk-*` variables each component exposes — see, for example, [ObjectTable › Theming](./ObjectTable.md#theming). The full catalog of variables lives in [CSSVariables.md](./CSSVariables.md).
+### Light and dark mode
+OSDK components ship a built-in dark theme. Wrap your app in `<OsdkThemeProvider>` to activate it and to let users override the OS preference at runtime:
+```tsx
+import { OsdkThemeProvider } from "@osdk/react-components/experimental/theme";
+function App() {
+  return (
+    <OsdkProvider client={client}>
+      <OsdkThemeProvider>
+        {/* defaults to "system" */}
+        {/* your app */}
+      </OsdkThemeProvider>
+    </OsdkProvider>
+  );
+}
+```
+By default the provider follows `prefers-color-scheme` and writes the resolved value to `data-bp-color-scheme` on `<html>` — matching [Blueprint's convention](https://blueprintjs.com/docs/#core/colors) so the theme also applies to portaled overlays (popovers, dialogs, tooltips).
+See [OsdkThemeProvider](./OsdkThemeProvider.md) for the full reference, including the `defaultTheme` modes, the `useOsdkTheme` hook, persisting the user's choice, and integrating with an external theme store via controlled mode.
 ### Accessibility
 When overriding theme tokens, keep the result accessible:

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@osdk/react-components",
-  "version": "0.19.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb",
+  "version": "0.19.0",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",
@@ -124,6 +124,15 @@
       "require": "./build/cjs/public/experimental/pdf-viewer.cjs",
       "default": "./build/browser/public/experimental/pdf-viewer.js"
     },
+    "./experimental/theme": {
+      "browser": "./build/browser/public/experimental/theme.js",
+      "import": {
+        "types": "./build/types/public/experimental/theme.d.ts",
+        "default": "./build/esm/public/experimental/theme.js"
+      },
+      "require": "./build/cjs/public/experimental/theme.cjs",
+      "default": "./build/browser/public/experimental/theme.js"
+    },
     "./experimental/tiff-renderer": {
       "browser": "./build/browser/public/experimental/tiff-renderer.js",
       "import": {
@@ -184,9 +193,9 @@
     "xlsx": "^0.18.5"
   },
   "peerDependencies": {
-    "@osdk/api": ">=2.23.0-beta.0",
-    "@osdk/client": ">=2.23.0-beta.0",
-    "@osdk/react": ">=2.23.0-beta.0",
+    "@osdk/api": "^2.8.0",
+    "@osdk/client": "^2.8.0",
+    "@osdk/react": "^2.8.0",
     "@types/react": "^17 || ^18 || ^19",
     "classnames": "^2.0.0",
     "react": "^17 || ^18 || ^19",
@@ -211,11 +220,11 @@
     "react-dom": "^18.3.1",
     "typescript": "~5.5.4",
     "@osdk/aip-core": "0.4.0",
-    "@osdk/client": "2.23.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb",
-    "@osdk/api": "2.23.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb",
+    "@osdk/api": "2.23.0",
+    "@osdk/client": "2.23.0",
     "@osdk/monorepo.api-extractor": "~0.7.0",
     "@osdk/monorepo.tsconfig": "~0.7.0",
-    "@osdk/react": "2.23.0-main-b5d7e7b9644f6f9d2b3771c6fafca28cd20a3cbb"
+    "@osdk/react": "2.23.0"
   },
   "publishConfig": {
     "access": "public"
@@ -240,7 +249,7 @@
   ],
   "type": "module",
   "scripts": {
-    "check-attw": "attw --pack . --exclude-entrypoints ./styles.css ./experimental/action-form ./experimental/aip-agent-chat ./experimental/document-viewer ./experimental/email-viewer ./experimental/excel-viewer ./experimental/filter-list ./experimental/image-viewer ./experimental/markdown-renderer ./experimental/object-table ./experimental/pdf-viewer ./experimental/tiff-renderer ./experimental/video-viewer ./experimental/xml-viewer",
+    "check-attw": "attw --pack . --exclude-entrypoints ./styles.css ./experimental/action-form ./experimental/aip-agent-chat ./experimental/document-viewer ./experimental/email-viewer ./experimental/excel-viewer ./experimental/filter-list ./experimental/image-viewer ./experimental/markdown-renderer ./experimental/object-table ./experimental/pdf-viewer ./experimental/theme ./experimental/tiff-renderer ./experimental/video-viewer ./experimental/xml-viewer",
     "check-spelling": "cspell --quiet .",
     "clean": "rm -rf lib dist types build tsconfig.tsbuildinfo",
     "fix-lint": "eslint . --fix && dprint fmt",

package/build/cjs/chunk-5NPRZBFO.cjs DELETED Viewed

@@ -1,11 +0,0 @@
-'use strict';
-var chunkKHMOMROL_cjs = require('./chunk-KHMOMROL.cjs');
-var chunkBBSLIWGB_cjs = require('./chunk-BBSLIWGB.cjs');
-// src/public/experimental/video-viewer.ts
-var VideoViewer2 = chunkBBSLIWGB_cjs.withOsdkMetrics(chunkKHMOMROL_cjs.VideoViewer, "VideoViewer");
-exports.VideoViewer = VideoViewer2;
-//# sourceMappingURL=chunk-5NPRZBFO.cjs.map
-//# sourceMappingURL=chunk-5NPRZBFO.cjs.map

package/build/cjs/chunk-6Z2CEPQP.cjs DELETED Viewed

@@ -1,11 +0,0 @@
-'use strict';
-var chunkVOROB7KJ_cjs = require('./chunk-VOROB7KJ.cjs');
-var chunkBBSLIWGB_cjs = require('./chunk-BBSLIWGB.cjs');
-// src/public/experimental/image-viewer.ts
-var ImageViewer2 = chunkBBSLIWGB_cjs.withOsdkMetrics(chunkVOROB7KJ_cjs.ImageViewer, "ImageViewer");
-exports.ImageViewer = ImageViewer2;
-//# sourceMappingURL=chunk-6Z2CEPQP.cjs.map
-//# sourceMappingURL=chunk-6Z2CEPQP.cjs.map

package/build/cjs/chunk-BBSLIWGB.cjs.map DELETED Viewed

@@ -1 +0,0 @@

- {"version":3,"sources":["../../src/util/UserAgent.ts","../../src/util/withOsdkMetrics.ts"],"names":["useRegisterUserAgent","React"],"mappings":";;;;;;;;;;;;AAgBA,IAAM,kBAAA,GAAqB,yBAAyB,sDAA2B,CAAA,CAAA;AACxE,SAAS,mBAAmB,aAAA,EAAe;AAChD,EAAA,OAAO,CAAA,EAAG,kBAAkB,CAAA,CAAA,EAAI,aAAa,CAAA,CAAA;AAC/C;;;ACKO,SAAS,eAAA,CAAgB,WAAW,IAAA,EAAM;AAC/C,EAAA,MAAM,UAAU,CAAA,KAAA,KAAS;AACvB,IAAAA,0BAAA,CAAqB,kBAAA,CAAmB,IAAI,CAAC,CAAA;AAC7C,IAAA,uBAAoBC,sBAAA,CAAM,aAAA,CAAc,SAAA,EAAW,KAAK,CAAA;AAAA,EAC1D,CAAA;AACA,EAAA,OAAA,CAAQ,WAAA,GAAc,mBAAmB,IAAI,CAAA,CAAA,CAAA;AAC7C,EAAA,OAAO,OAAA;AACT","file":"chunk-BBSLIWGB.cjs","sourcesContent":["/*\n * Copyright 2025 Palantir Technologies, Inc. All rights reserved.\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n * http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n\nconst PACKAGE_USER_AGENT = `osdk-react-components/${process.env.PACKAGE_VERSION}`;\nexport function componentUserAgent(componentName) {\n return `${PACKAGE_USER_AGENT}/${componentName}`;\n}","/*\n * Copyright 2026 Palantir Technologies, Inc. All rights reserved.\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n * http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n\nimport { useRegisterUserAgent } from \"@osdk/react\";\nimport React from \"react\";\nimport { componentUserAgent } from \"./UserAgent.js\";\n\n// `any` is required: FunctionComponent defaults to FunctionComponent<{}> which\n// rejects components with required props. A generic P parameter doesn't help\n// because TS can't infer both P and C simultaneously from a single argument.\n// eslint-disable-next-line @typescript-eslint/no-explicit-any\nexport function withOsdkMetrics(Component, name) {\n const Wrapped = props => {\n useRegisterUserAgent(componentUserAgent(name));\n return /*#__PURE__*/React.createElement(Component, props);\n };\n Wrapped.displayName = `withOsdkMetrics(${name})`;\n return Wrapped;\n}"]}

package/build/cjs/chunk-C6IVBY3E.cjs DELETED Viewed

@@ -1,11 +0,0 @@
-'use strict';
-var chunkPKJFOG2Z_cjs = require('./chunk-PKJFOG2Z.cjs');
-var chunkBBSLIWGB_cjs = require('./chunk-BBSLIWGB.cjs');
-// src/public/experimental/email-viewer.ts
-var EmailViewer2 = chunkBBSLIWGB_cjs.withOsdkMetrics(chunkPKJFOG2Z_cjs.EmailViewer, "EmailViewer");
-exports.EmailViewer = EmailViewer2;
-//# sourceMappingURL=chunk-C6IVBY3E.cjs.map
-//# sourceMappingURL=chunk-C6IVBY3E.cjs.map

package/build/cjs/chunk-G2AYUCKB.cjs DELETED Viewed

@@ -1,11 +0,0 @@
-'use strict';
-var chunkOUJQJQ7N_cjs = require('./chunk-OUJQJQ7N.cjs');
-var chunkBBSLIWGB_cjs = require('./chunk-BBSLIWGB.cjs');
-// src/public/experimental/xml-viewer.ts
-var XmlViewer2 = chunkBBSLIWGB_cjs.withOsdkMetrics(chunkOUJQJQ7N_cjs.XmlViewer, "XmlViewer");
-exports.XmlViewer = XmlViewer2;
-//# sourceMappingURL=chunk-G2AYUCKB.cjs.map
-//# sourceMappingURL=chunk-G2AYUCKB.cjs.map