@cognite/aura 0.3.5 → 1.46104.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Cognite AS
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -4,13 +4,14 @@ Aura exports Cognite's UI components, styles, utilities, and ESLint guidance for
 
 ## Using Aura in Fusion
 
-[`DESIGN.md`](./DESIGN.md) describes visual identity, critical interaction rules, and UX guidance for feedback, disclosure, errors, layout, and accessibility. This section covers *how to use the package* in the Fusion monorepo and host shell.
+[`DESIGN.md`](./DESIGN.md) describes visual identity, critical interaction rules, and UX guidance for feedback, disclosure, errors, layout, and accessibility.
+This section covers _how to use the package_ in the Fusion monorepo and host shell.
 
 ### Package imports
 
 Aura ships two flavours of component import. Both resolve through the package's `exports` map — never reach into `src/`.
 
-**Per-component subpath (strongly preferred for app code)** keeps bundles small *and* keeps builds fast by only pulling in what each module actually needs:
+**Per-component subpath (strongly preferred for app code)** keeps bundles small _and_ keeps builds fast by only pulling in what each module actually needs:
 
 ```tsx
 import { Button } from '@cognite/aura/components/button';
@@ -24,7 +25,12 @@ import { DatePicker } from '@cognite/aura/components/date-time-pickers';
 import { Button, Card } from '@cognite/aura/components';
 ```
 
-> ⚠️ **The barrel is not free at build time.** Even though the runtime output tree-shakes (the barrel is side-effect-free apart from `*.css`), a bundler must still *load and transform* every module the barrel re-exports before tree-shaking can drop the unused ones. That includes heavy graphs such as `shiki` (via `CodeBlock`) and `mermaid` + `streamdown` (via `Message`). For a small app this can mean transforming ~10k modules and exhausting the default Node heap (`JavaScript heap out of memory`). Reaching for a single component from the barrel (`import { Card } from '@cognite/aura/components'`) pays this whole cost. Use per-component subpaths in app code; reserve the barrel for stories/prototypes.
+> ⚠️ **The barrel is not free at build time.**
+> Even though the runtime output tree-shakes (the barrel is side-effect-free apart from `*.css`), a bundler must still _load and transform_ every module the barrel re-exports before tree-shaking can drop the unused ones.
+> That includes heavy graphs such as `shiki` (via `CodeBlock`) and `mermaid` + `streamdown` (via `Message`).
+> For a small app this can mean transforming ~10k modules and exhausting the default Node heap (`JavaScript heap out of memory`).
+> Reaching for a single component from the barrel (`import { Card } from '@cognite/aura/components'`) pays this whole cost.
+> Use per-component subpaths in app code; reserve the barrel for stories/prototypes.
 
 Lightweight components never pull the heavy graphs: `shiki` is only imported by `@cognite/aura/components/code-block`, and `mermaid`/`streamdown` only by `@cognite/aura/components/message`. Importing e.g. `@cognite/aura/components/card` (or the shared `@cognite/aura/utils` `cn` helper) pulls neither — the `cn` helper is deliberately kept in a module that has no path to `shiki`.
 
@@ -109,13 +115,13 @@ Prefer **CVA** variants and component APIs over overriding primitive styles. Pro
 
 The Fusion host shell owns global chrome that Aura does not ship: **Topbar**, **Sonner** toasts, **AlertDialog**, **Sheet** / **Drawer**, **Tabs**, **SegmentedControl**, and some patterns like **EmptyState**. These **must** still follow Aura tokens, [Interaction states](./DESIGN.md#interaction-states), and [Heuristics](./DESIGN.md#heuristics).
 
-| Concern | Fusion convention |
-| ------- | ----------------- |
-| Primary navigation | One **Topbar**; avoid duplicating global nav in content |
-| View switching | Shell **Tabs** / **SegmentedControl** when the product uses that pattern |
-| Toasts | **Sonner**, bottom-right, ~4s auto-dismiss, themed with Aura tokens |
-| Confirm destructive work | Shell **AlertDialog** or Aura **Dialog** with explicit copy |
-| Narrow viewports | Prefer shell **Drawer** / **Dialog** over compressed multi-column chrome |
+| Concern                  | Fusion convention                                                        |
+| ------------------------ | ------------------------------------------------------------------------ |
+| Primary navigation       | One **Topbar**; avoid duplicating global nav in content                  |
+| View switching           | Shell **Tabs** / **SegmentedControl** when the product uses that pattern |
+| Toasts                   | **Sonner**, bottom-right, ~4s auto-dismiss, themed with Aura tokens      |
+| Confirm destructive work | Shell **AlertDialog** or Aura **Dialog** with explicit copy              |
+| Narrow viewports         | Prefer shell **Drawer** / **Dialog** over compressed multi-column chrome |
 
 For local sub-app development against the live shell, use import map overrides — see the Fusion [subapp manual testing guide](../../.cursor/rules/subapp-manual-testing.mdc).
 
@@ -143,11 +149,12 @@ Some Aura entry points require optional peer dependencies that consumers must in
   import {
     ChartContainer,
     ChartTooltip,
+    chartSeriesColor,
     type ChartConfig,
   } from '@cognite/aura/chart';
 
   const config = {
-    runs: { label: 'Runs', color: 'var(--color-chart-fjord-color-1)' },
+    runs: { label: 'Runs', color: chartSeriesColor(1) },
   } satisfies ChartConfig;
 
   <ChartContainer config={config} aria-label="Runs by day">
@@ -156,7 +163,7 @@ Some Aura entry points require optional peer dependencies that consumers must in
       <ChartTooltip />
       <Bar dataKey="runs" fill="var(--color-runs)" />
     </BarChart>
-  </ChartContainer>
+  </ChartContainer>;
   ```
 
 - `@cognite/aura/data-grid` requires `@tanstack/react-table >=8.7` and `@tanstack/react-virtual >=3.10`. Add them to your app:
@@ -205,7 +212,8 @@ Ensure all documentation is up to date before bumping the version:
 
 ### After publishing
 
-Consumers can adopt the new version by updating their `package.json` manually, or by letting Renovate/Dependabot open a bump PR in their repo automatically. [The Custom Apps repo](https://github.com/cognitedata/dune) has this configured and is the primary critical consumer. 
+Consumers can adopt the new version by updating their `package.json` manually, or by letting Renovate/Dependabot open a bump PR in their repo automatically.
+[The Custom Apps repo](https://github.com/cognitedata/dune) has this configured and is the primary critical consumer.
 
 ## DESIGN.md