@commercetools/nimbus-mcp 0.1.0 → 2.10.0

package/data/docs/routes/home-getting-started-release-process.json

@@ -0,0 +1,294 @@
+{
+  "meta": {
+    "id": "Home-Release-Process",
+    "title": "Release Process",
+    "description": "How Nimbus releases work and how to stay informed",
+    "order": 4,
+    "repoPath": "packages/nimbus/src/docs/release.mdx",
+    "menu": [
+      "Home",
+      "Getting Started",
+      "Release Process"
+    ],
+    "route": "home/getting-started/release-process",
+    "tags": [
+      "releases",
+      "versioning",
+      "upgrades",
+      "support"
+    ],
+    "toc": [
+      {
+        "value": "Release Cadence",
+        "href": "#release-cadence",
+        "depth": 2,
+        "numbering": [
+          1,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "How to Stay Informed",
+        "href": "#how-to-stay-informed",
+        "depth": 2,
+        "numbering": [
+          1,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Communication Channels",
+        "href": "#communication-channels",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Announcement Format",
+        "href": "#announcement-format",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "If Something Goes Wrong",
+        "href": "#if-something-goes-wrong",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Getting Support",
+        "href": "#getting-support",
+        "depth": 2,
+        "numbering": [
+          1,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Self-Service Resources",
+        "href": "#self-service-resources",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Asking for Help",
+        "href": "#asking-for-help",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "What We Can Help With",
+        "href": "#what-we-can-help-with",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "What We Can't Help With",
+        "href": "#what-we-cant-help-with",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Documentation Standards",
+        "href": "#documentation-standards",
+        "depth": 2,
+        "numbering": [
+          1,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Questions?",
+        "href": "#questions",
+        "depth": 2,
+        "numbering": [
+          1,
+          5
+        ],
+        "parent": "root"
+      }
+    ],
+    "icon": "NewReleases",
+    "layout": "app-frame",
+    "tabs": [
+      {
+        "key": "overview",
+        "title": "Overview",
+        "order": 0
+      }
+    ]
+  },
+  "mdx": "\n# Release Process\n\nThis page explains how Nimbus releases work, what to expect from each release\ntype, and how to stay informed about changes that may affect your application.\n\n## Release Cadence\n\nNimbus follows [Semantic Versioning](https://semver.org/):\n\n| Release Type      | Frequency    | Contents                           |\n| ----------------- | ------------ | ---------------------------------- |\n| **Major (X.0.0)** | As needed    | Breaking changes, major features   |\n| **Minor (x.Y.0)** | As needed    | New features, non-breaking changes |\n| **Patch (x.x.Z)** | As needed    | Bug fixes, security patches        |\n\nWe release when there's something to release. Deprecation warnings include\nspecific sunset dates so you can plan ahead.\n\n## How to Stay Informed\n\n### Communication Channels\n\n| Channel                                                                        | What You'll Find                     |\n| ------------------------------------------------------------------------------ | ------------------------------------ |\n| [**Changelog**](https://github.com/commercetools/nimbus/releases)        | Release announcements, changelog     |\n| [**GitHub Issues**](https://github.com/commercetools/nimbus/issues)            | Bug reports, feature requests        |\n| [**GitHub Discussions**](https://github.com/commercetools/nimbus/discussions)  | Questions, major release Q&A         |\n| **#ask-nimbus-anything** (Slack)                                               | General questions                    |\n\n### Announcement Format\n\nAll release announcements follow a consistent format:\n\n- Version number and release type\n- Summary of changes (3-5 bullet points)\n- Link to full changelog\n- Migration guide (if applicable)\n- Thread for questions\n\n### If Something Goes Wrong\n\nIf a release introduces a critical issue:\n\n1. We'll create a [GitHub issue](https://github.com/commercetools/nimbus/issues) documenting the problem\n2. We'll publish a patch that reverts the problematic changes\n3. We'll communicate in #ask-nimbus-anything linking to the issue\n\n## Getting Support\n\n### Self-Service Resources\n\nMost questions can be answered through our documentation:\n\n- **Component documentation** — Usage examples and API reference\n- **Storybook** — Interactive examples and visual testing\n- **Changelog** — Detailed list of all changes\n- **Migration guides** — Step-by-step upgrade instructions\n\n### Asking for Help\n\nIf you can't find what you need in the docs:\n\n1. **Search GitHub Issues and Discussions** — Your question may have been answered before\n2. **File an Issue or start a Discussion** — We aim to respond within 24 hours\n3. **Internal developers**: also try #ask-nimbus-anything for quick questions\n\n### What We Can Help With\n\n- Clarifying documentation or API behavior\n- Debugging issues with Nimbus components\n- Migration guidance for breaking changes\n- Feature requests and feedback\n\n### What We Can't Help With\n\n- Updating your application code for you\n- Debugging issues in your application unrelated to Nimbus\n- Guaranteeing specific timelines for feature requests (though we do consider\n  urgency when planning our roadmap)\n\n## Documentation Standards\n\nWe maintain documentation alongside code changes:\n\n| Change Type      | Documentation Provided                              |\n| ---------------- | --------------------------------------------------- |\n| New component    | Full docs (examples, API reference) before release  |\n| New prop/feature | Updated component docs in the same release          |\n| Deprecation      | Deprecation notice with timeline and migration path |\n| Breaking change  | Migration guide with before/after examples          |\n| Bug fix          | Changelog entry                                     |\n\n## Questions?\n\n- **Questions & discussions**: [GitHub Discussions](https://github.com/commercetools/nimbus/discussions)\n- **Bugs & feature requests**: [GitHub Issues](https://github.com/commercetools/nimbus/issues)\n- **Internal quick questions**: #ask-nimbus-anything\n",
+  "views": {
+    "overview": {
+      "mdx": "\n# Release Process\n\nThis page explains how Nimbus releases work, what to expect from each release\ntype, and how to stay informed about changes that may affect your application.\n\n## Release Cadence\n\nNimbus follows [Semantic Versioning](https://semver.org/):\n\n| Release Type      | Frequency    | Contents                           |\n| ----------------- | ------------ | ---------------------------------- |\n| **Major (X.0.0)** | As needed    | Breaking changes, major features   |\n| **Minor (x.Y.0)** | As needed    | New features, non-breaking changes |\n| **Patch (x.x.Z)** | As needed    | Bug fixes, security patches        |\n\nWe release when there's something to release. Deprecation warnings include\nspecific sunset dates so you can plan ahead.\n\n## How to Stay Informed\n\n### Communication Channels\n\n| Channel                                                                        | What You'll Find                     |\n| ------------------------------------------------------------------------------ | ------------------------------------ |\n| [**Changelog**](https://github.com/commercetools/nimbus/releases)        | Release announcements, changelog     |\n| [**GitHub Issues**](https://github.com/commercetools/nimbus/issues)            | Bug reports, feature requests        |\n| [**GitHub Discussions**](https://github.com/commercetools/nimbus/discussions)  | Questions, major release Q&A         |\n| **#ask-nimbus-anything** (Slack)                                               | General questions                    |\n\n### Announcement Format\n\nAll release announcements follow a consistent format:\n\n- Version number and release type\n- Summary of changes (3-5 bullet points)\n- Link to full changelog\n- Migration guide (if applicable)\n- Thread for questions\n\n### If Something Goes Wrong\n\nIf a release introduces a critical issue:\n\n1. We'll create a [GitHub issue](https://github.com/commercetools/nimbus/issues) documenting the problem\n2. We'll publish a patch that reverts the problematic changes\n3. We'll communicate in #ask-nimbus-anything linking to the issue\n\n## Getting Support\n\n### Self-Service Resources\n\nMost questions can be answered through our documentation:\n\n- **Component documentation** — Usage examples and API reference\n- **Storybook** — Interactive examples and visual testing\n- **Changelog** — Detailed list of all changes\n- **Migration guides** — Step-by-step upgrade instructions\n\n### Asking for Help\n\nIf you can't find what you need in the docs:\n\n1. **Search GitHub Issues and Discussions** — Your question may have been answered before\n2. **File an Issue or start a Discussion** — We aim to respond within 24 hours\n3. **Internal developers**: also try #ask-nimbus-anything for quick questions\n\n### What We Can Help With\n\n- Clarifying documentation or API behavior\n- Debugging issues with Nimbus components\n- Migration guidance for breaking changes\n- Feature requests and feedback\n\n### What We Can't Help With\n\n- Updating your application code for you\n- Debugging issues in your application unrelated to Nimbus\n- Guaranteeing specific timelines for feature requests (though we do consider\n  urgency when planning our roadmap)\n\n## Documentation Standards\n\nWe maintain documentation alongside code changes:\n\n| Change Type      | Documentation Provided                              |\n| ---------------- | --------------------------------------------------- |\n| New component    | Full docs (examples, API reference) before release  |\n| New prop/feature | Updated component docs in the same release          |\n| Deprecation      | Deprecation notice with timeline and migration path |\n| Breaking change  | Migration guide with before/after examples          |\n| Bug fix          | Changelog entry                                     |\n\n## Questions?\n\n- **Questions & discussions**: [GitHub Discussions](https://github.com/commercetools/nimbus/discussions)\n- **Bugs & feature requests**: [GitHub Issues](https://github.com/commercetools/nimbus/issues)\n- **Internal quick questions**: #ask-nimbus-anything\n",
+      "toc": [
+        {
+          "value": "Release Cadence",
+          "href": "#release-cadence",
+          "depth": 2,
+          "numbering": [
+            1,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "How to Stay Informed",
+          "href": "#how-to-stay-informed",
+          "depth": 2,
+          "numbering": [
+            1,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Communication Channels",
+          "href": "#communication-channels",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Announcement Format",
+          "href": "#announcement-format",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "If Something Goes Wrong",
+          "href": "#if-something-goes-wrong",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Getting Support",
+          "href": "#getting-support",
+          "depth": 2,
+          "numbering": [
+            1,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Self-Service Resources",
+          "href": "#self-service-resources",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Asking for Help",
+          "href": "#asking-for-help",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "What We Can Help With",
+          "href": "#what-we-can-help-with",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "What We Can't Help With",
+          "href": "#what-we-cant-help-with",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Documentation Standards",
+          "href": "#documentation-standards",
+          "depth": 2,
+          "numbering": [
+            1,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Questions?",
+          "href": "#questions",
+          "depth": 2,
+          "numbering": [
+            1,
+            5
+          ],
+          "parent": "root"
+        }
+      ]
+    }
+  }
+}

package/data/docs/routes/home-getting-started-testing-setup.json

@@ -0,0 +1,296 @@
+{
+  "meta": {
+    "id": "Home-Testing-Setup",
+    "title": "Testing Setup",
+    "description": "Configure Jest or Vitest to test Nimbus components",
+    "order": 1.6,
+    "repoPath": "packages/nimbus/src/docs/home-testing-setup.mdx",
+    "menu": [
+      "Home",
+      "Getting Started",
+      "Testing Setup"
+    ],
+    "route": "home/getting-started/testing-setup",
+    "tags": [
+      "guide",
+      "testing",
+      "jest",
+      "vitest"
+    ],
+    "toc": [
+      {
+        "value": "Why JSDOM Polyfills?",
+        "href": "#why-jsdom-polyfills",
+        "depth": 2,
+        "numbering": [
+          1,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Jest Setup",
+        "href": "#jest-setup",
+        "depth": 2,
+        "numbering": [
+          1,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "1. Add Polyfills to Setup Files",
+        "href": "#1-add-polyfills-to-setup-files",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Complete Example",
+        "href": "#complete-example",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "2. Write Tests",
+        "href": "#2-write-tests",
+        "depth": 3,
+        "numbering": [
+          1,
+          2,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Vitest Setup",
+        "href": "#vitest-setup",
+        "depth": 2,
+        "numbering": [
+          1,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "1. Add Polyfills to Setup Files",
+        "href": "#1-add-polyfills-to-setup-files-1",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Complete Example",
+        "href": "#complete-example-1",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "2. Write Tests",
+        "href": "#2-write-tests-1",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Testing Best Practices",
+        "href": "#testing-best-practices",
+        "depth": 2,
+        "numbering": [
+          1,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Always Use NimbusProvider",
+        "href": "#always-use-nimbusprovider",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Create a Test Utility",
+        "href": "#create-a-test-utility",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          2
+        ],
+        "parent": "root"
+      }
+    ],
+    "icon": "Science",
+    "layout": "app-frame",
+    "tabs": [
+      {
+        "key": "overview",
+        "title": "Overview",
+        "order": 0
+      }
+    ]
+  },
+  "mdx": "\n# Testing Setup\n\nNimbus components require specific polyfills to work in JSDOM test environments (Jest, Vitest). This guide shows you how to configure your test runner to work with Nimbus.\n\n## Why JSDOM Polyfills?\n\nJSDOM is a headless browser environment used by Jest and Vitest. It doesn't include all browser APIs that Chakra UI and React Aria (which Nimbus is built on) depend on. Nimbus provides polyfills for these missing APIs.\n\nThe polyfills include:\n- `structuredClone` - Required by Chakra UI for theme configuration\n- `window.matchMedia` - Required for responsive design and color mode\n- `ResizeObserver` - Required for responsive components\n- `IntersectionObserver` - Required for lazy loading and viewport tracking\n- `Element.prototype.scrollTo/scrollIntoView` - Required for focus management\n- `requestAnimationFrame` - Required for animations and transitions\n\n## Jest Setup\n\n### 1. Add Polyfills to Setup Files\n\nAdd Nimbus polyfills to your Jest configuration's `setupFiles` array:\n\n```javascript\n// jest.config.js\nmodule.exports = {\n  setupFiles: [\n    '@commercetools/nimbus/setup-jsdom-polyfills'\n  ]\n};\n```\n\n### Complete Example\n\n```javascript\n// jest.config.js\nmodule.exports = {\n  testEnvironment: 'jsdom',\n  setupFiles: [\n    // Add Nimbus polyfills BEFORE other setup files\n    '@commercetools/nimbus/setup-jsdom-polyfills'\n  ],\n  setupFilesAfterEnv: [\n    '@testing-library/jest-dom',\n  ],\n  moduleNameMapper: {\n    '\\\\.(css|less|scss|sass)$': 'identity-obj-proxy',\n  },\n};\n```\n\n### 2. Write Tests\n\nWith the polyfills configured, you can test Nimbus components:\n\n```typescript\n// button.test.tsx\nimport { render, screen } from '@testing-library/react';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { Button } from '@commercetools/nimbus';\n\ndescribe('Button', () => {\n  it('renders button text', () => {\n    render(\n      <NimbusProvider>\n        <Button>Click me</Button>\n      </NimbusProvider>\n    );\n\n    expect(screen.getByRole('button', { name: 'Click me' })).toBeInTheDocument();\n  });\n});\n```\n\n> [!IMPORTANT]  \n> Always wrap your components in `<NimbusProvider>` when testing, just like in your application.\n\n## Vitest Setup\n\n### 1. Add Polyfills to Setup Files\n\nAdd Nimbus polyfills to your Vitest configuration:\n\n```typescript\n// vitest.config.ts\nimport { defineConfig } from 'vitest/config';\n\nexport default defineConfig({\n  test: {\n    environment: 'jsdom',\n    setupFiles: [\n      '@commercetools/nimbus/setup-jsdom-polyfills'\n    ],\n  },\n});\n```\n\n### Complete Example\n\n```typescript\n// vitest.config.ts\nimport { defineConfig } from 'vitest/config';\nimport react from '@vitejs/plugin-react';\n\nexport default defineConfig({\n  plugins: [react()],\n  test: {\n    environment: 'jsdom',\n    setupFiles: [\n      // Add Nimbus polyfills\n      '@commercetools/nimbus/setup-jsdom-polyfills',\n      // Add other setup files\n      './test/setup.ts',\n    ],\n    globals: true,\n  },\n});\n```\n\n### 2. Write Tests\n\n```typescript\n// button.test.tsx\nimport { render, screen } from '@testing-library/react';\nimport { describe, it, expect } from 'vitest';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { Button } from '@commercetools/nimbus';\n\ndescribe('Button', () => {\n  it('renders button text', () => {\n    render(\n      <NimbusProvider>\n        <Button>Click me</Button>\n      </NimbusProvider>\n    );\n\n    expect(screen.getByRole('button', { name: 'Click me' })).toBeInTheDocument();\n  });\n});\n```\n\n## Testing Best Practices\n\n### Always Use NimbusProvider\n\nWrap your test components in `NimbusProvider`:\n\n```typescript\n// ✅ Correct\nrender(\n  <NimbusProvider>\n    <YourComponent />\n  </NimbusProvider>\n);\n\n// ❌ Incorrect - will cause errors\nrender(<YourComponent />);\n```\n\n### Create a Test Utility\n\nFor convenience, create a custom render function:\n\n```typescript\n// test-utils.tsx\nimport { render, RenderOptions } from '@testing-library/react';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { ReactElement } from 'react';\n\nexport function renderWithNimbus(\n  ui: ReactElement,\n  options?: RenderOptions\n) {\n  return render(ui, {\n    wrapper: ({ children }) => <NimbusProvider>{children}</NimbusProvider>,\n    ...options,\n  });\n}\n\n// Usage in tests\nimport { renderWithNimbus } from './test-utils';\n\nrenderWithNimbus(<Button>Click me</Button>);\n```\n",
+  "views": {
+    "overview": {
+      "mdx": "\n# Testing Setup\n\nNimbus components require specific polyfills to work in JSDOM test environments (Jest, Vitest). This guide shows you how to configure your test runner to work with Nimbus.\n\n## Why JSDOM Polyfills?\n\nJSDOM is a headless browser environment used by Jest and Vitest. It doesn't include all browser APIs that Chakra UI and React Aria (which Nimbus is built on) depend on. Nimbus provides polyfills for these missing APIs.\n\nThe polyfills include:\n- `structuredClone` - Required by Chakra UI for theme configuration\n- `window.matchMedia` - Required for responsive design and color mode\n- `ResizeObserver` - Required for responsive components\n- `IntersectionObserver` - Required for lazy loading and viewport tracking\n- `Element.prototype.scrollTo/scrollIntoView` - Required for focus management\n- `requestAnimationFrame` - Required for animations and transitions\n\n## Jest Setup\n\n### 1. Add Polyfills to Setup Files\n\nAdd Nimbus polyfills to your Jest configuration's `setupFiles` array:\n\n```javascript\n// jest.config.js\nmodule.exports = {\n  setupFiles: [\n    '@commercetools/nimbus/setup-jsdom-polyfills'\n  ]\n};\n```\n\n### Complete Example\n\n```javascript\n// jest.config.js\nmodule.exports = {\n  testEnvironment: 'jsdom',\n  setupFiles: [\n    // Add Nimbus polyfills BEFORE other setup files\n    '@commercetools/nimbus/setup-jsdom-polyfills'\n  ],\n  setupFilesAfterEnv: [\n    '@testing-library/jest-dom',\n  ],\n  moduleNameMapper: {\n    '\\\\.(css|less|scss|sass)$': 'identity-obj-proxy',\n  },\n};\n```\n\n### 2. Write Tests\n\nWith the polyfills configured, you can test Nimbus components:\n\n```typescript\n// button.test.tsx\nimport { render, screen } from '@testing-library/react';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { Button } from '@commercetools/nimbus';\n\ndescribe('Button', () => {\n  it('renders button text', () => {\n    render(\n      <NimbusProvider>\n        <Button>Click me</Button>\n      </NimbusProvider>\n    );\n\n    expect(screen.getByRole('button', { name: 'Click me' })).toBeInTheDocument();\n  });\n});\n```\n\n> [!IMPORTANT]  \n> Always wrap your components in `<NimbusProvider>` when testing, just like in your application.\n\n## Vitest Setup\n\n### 1. Add Polyfills to Setup Files\n\nAdd Nimbus polyfills to your Vitest configuration:\n\n```typescript\n// vitest.config.ts\nimport { defineConfig } from 'vitest/config';\n\nexport default defineConfig({\n  test: {\n    environment: 'jsdom',\n    setupFiles: [\n      '@commercetools/nimbus/setup-jsdom-polyfills'\n    ],\n  },\n});\n```\n\n### Complete Example\n\n```typescript\n// vitest.config.ts\nimport { defineConfig } from 'vitest/config';\nimport react from '@vitejs/plugin-react';\n\nexport default defineConfig({\n  plugins: [react()],\n  test: {\n    environment: 'jsdom',\n    setupFiles: [\n      // Add Nimbus polyfills\n      '@commercetools/nimbus/setup-jsdom-polyfills',\n      // Add other setup files\n      './test/setup.ts',\n    ],\n    globals: true,\n  },\n});\n```\n\n### 2. Write Tests\n\n```typescript\n// button.test.tsx\nimport { render, screen } from '@testing-library/react';\nimport { describe, it, expect } from 'vitest';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { Button } from '@commercetools/nimbus';\n\ndescribe('Button', () => {\n  it('renders button text', () => {\n    render(\n      <NimbusProvider>\n        <Button>Click me</Button>\n      </NimbusProvider>\n    );\n\n    expect(screen.getByRole('button', { name: 'Click me' })).toBeInTheDocument();\n  });\n});\n```\n\n## Testing Best Practices\n\n### Always Use NimbusProvider\n\nWrap your test components in `NimbusProvider`:\n\n```typescript\n// ✅ Correct\nrender(\n  <NimbusProvider>\n    <YourComponent />\n  </NimbusProvider>\n);\n\n// ❌ Incorrect - will cause errors\nrender(<YourComponent />);\n```\n\n### Create a Test Utility\n\nFor convenience, create a custom render function:\n\n```typescript\n// test-utils.tsx\nimport { render, RenderOptions } from '@testing-library/react';\nimport { NimbusProvider } from '@commercetools/nimbus';\nimport { ReactElement } from 'react';\n\nexport function renderWithNimbus(\n  ui: ReactElement,\n  options?: RenderOptions\n) {\n  return render(ui, {\n    wrapper: ({ children }) => <NimbusProvider>{children}</NimbusProvider>,\n    ...options,\n  });\n}\n\n// Usage in tests\nimport { renderWithNimbus } from './test-utils';\n\nrenderWithNimbus(<Button>Click me</Button>);\n```\n",
+      "toc": [
+        {
+          "value": "Why JSDOM Polyfills?",
+          "href": "#why-jsdom-polyfills",
+          "depth": 2,
+          "numbering": [
+            1,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Jest Setup",
+          "href": "#jest-setup",
+          "depth": 2,
+          "numbering": [
+            1,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "1. Add Polyfills to Setup Files",
+          "href": "#1-add-polyfills-to-setup-files",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Complete Example",
+          "href": "#complete-example",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "2. Write Tests",
+          "href": "#2-write-tests",
+          "depth": 3,
+          "numbering": [
+            1,
+            2,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Vitest Setup",
+          "href": "#vitest-setup",
+          "depth": 2,
+          "numbering": [
+            1,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "1. Add Polyfills to Setup Files",
+          "href": "#1-add-polyfills-to-setup-files-1",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Complete Example",
+          "href": "#complete-example-1",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "2. Write Tests",
+          "href": "#2-write-tests-1",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Testing Best Practices",
+          "href": "#testing-best-practices",
+          "depth": 2,
+          "numbering": [
+            1,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Always Use NimbusProvider",
+          "href": "#always-use-nimbusprovider",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Create a Test Utility",
+          "href": "#create-a-test-utility",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            2
+          ],
+          "parent": "root"
+        }
+      ]
+    }
+  }
+}