@maggioli-design-system/magma-react 2.5.1 → 2.7.0

package/agents/lint.md

@@ -0,0 +1,298 @@
+<!--
+  GENERATED FILE - do not edit by hand.
+  Source of truth: docs/agents/ in the magma monorepo.
+  Regenerate with: npm run sync.agent-docs (from the stencil package).
+-->
+# Magma lint
+
+> Scope: checking the code you write against the installed Magma, with the ESLint and
+> Stylelint rules that ship inside `@maggioli-design-system/magma`. Set them up once, when
+> you install Magma, and run them after every change.
+
+The rules make the prose of these guides executable: a prop value the component does not
+take, a boolean turned "off" with `"false"`, an icon-only control without a name, a colour
+painted with Tailwind's palette or a raw palette step, a hand-written dark mode. They read
+the API and the tokens of the installed version, the same release as the components, so
+they follow every update with nothing to keep in sync.
+
+## Set it up
+
+Nothing to install from Magma: the rules are in `@maggioli-design-system/magma`, which
+`magma-react` and `magma-angular` require too. The project needs ESLint 9 and Stylelint 16
+(`npm i -D eslint stylelint` when it has none) and the parser of its templates:
+
+| Templates | Parser |
+| --- | --- |
+| HTML | `@html-eslint/parser` |
+| Angular (external `.html` templates) | `@angular-eslint/template-parser` (with angular-eslint) |
+| React (JSX, TSX) | the one the project already uses |
+
+MERGE the blocks below into the project's `eslint.config.js` and `stylelint.config.mjs`:
+never replace an existing configuration. Each ESLint preset sets rules only, so it goes in
+the block that parses the templates.
+
+### HTML and web components
+
+```js
+// eslint.config.js
+import html from '@html-eslint/parser';
+import magma from '@maggioli-design-system/magma/eslint';
+
+export default [
+  { files: ['**/*.html'], languageOptions: { parser: html }, ...magma.configs.recommended },
+];
+```
+
+### React
+
+```js
+// eslint.config.js
+import magma from '@maggioli-design-system/magma/eslint';
+
+export default [
+  // ...the block that parses .jsx and .tsx
+  { files: ['**/*.{jsx,tsx}'], ...magma.configs.recommended },
+];
+```
+
+The rules read both `<mds-button>` and the wrappers of `magma-react` (`<MdsButton>`), and the
+classes of a `className` wherever its expression writes them, `clsx()` and ternaries included
+(see [`no-raw-palette-classes`](#no-raw-palette-classes)).
+
+### Angular
+
+```js
+// eslint.config.js, next to the blocks of angular-eslint
+import angularTemplate from '@angular-eslint/template-parser';
+import magma from '@maggioli-design-system/magma/eslint';
+
+export default [
+  { files: ['**/*.html'], languageOptions: { parser: angularTemplate }, ...magma.configs.recommended },
+];
+```
+
+With the inline-template processor of angular-eslint, the inline `template` of a component
+is linted as an `.html` file too.
+
+### CSS and SCSS
+
+```js
+// stylelint.config.mjs
+export default {
+  extends: ['@maggioli-design-system/magma/stylelint/recommended'],
+};
+```
+
+### Presets
+
+- `recommended`, for a product that already exists: what is broken or not accessible is an
+  error, the palette and an internal custom property a warning;
+- `strict` (`magma.configs.strict`, `@maggioli-design-system/magma/stylelint/strict`), for a
+  new product: every rule is an error.
+
+## Run it after writing
+
+After every change, run ESLint on the templates you touched and Stylelint on the
+stylesheets, and fix what they report before you hand the work over:
+
+```bash
+npx eslint src
+npx stylelint "src/**/*.{css,scss}"
+```
+
+An error is something broken or not accessible; a warning of `recommended` is a colour that
+does not follow the mode, the named theme and the contrast preference, or a custom property a
+component may change in any release. When a rule is wrong about Magma itself, report it
+([`reporting.md`](reporting.md)) instead of disabling it.
+
+## Rules
+
+| Rule | Tool | `recommended` | `strict` |
+| --- | --- | --- | --- |
+| [`valid-attribute-values`](#valid-attribute-values) | ESLint | error | error |
+| [`no-false-boolean`](#no-false-boolean) | ESLint | error | error |
+| [`accessible-name`](#accessible-name) | ESLint | error | error |
+| [`no-raw-palette-classes`](#no-raw-palette-classes) | ESLint, Stylelint | warn | error |
+| [`no-color-scheme-override`](#no-color-scheme-override) | Stylelint | error | error |
+| [`no-raw-color`](#no-raw-color) | Stylelint | warning | error |
+| [`no-internal-tokens`](#no-internal-tokens) | ESLint, Stylelint | warn | error |
+
+The ESLint rules are named `magma/<rule>` once the preset is loaded, the Stylelint rules
+`magma/<rule>` once the plugin (`@maggioli-design-system/magma/stylelint`) is.
+
+### valid-attribute-values
+
+A prop whose type is a union of literals takes one of them (the values each prop takes are
+in the component's `AGENTS.md`).
+
+```html
+<!-- INCORRECT: tone takes "box", "strong" or "weak" -->
+<mds-banner tone="outline">Saved</mds-banner>
+
+<!-- CORRECT -->
+<mds-banner tone="weak">Saved</mds-banner>
+```
+
+A value bound to an expression (`[tone]="tone"`, `tone={tone}`) is known only at run time and
+is not checked; a literal binding (`[tone]="'box'"`) is.
+
+### no-false-boolean
+
+A boolean prop is turned off by removing its attribute
+([`conventions.md`](conventions.md#boolean-disabled-and-await-props)): a form-associated
+component reads any value as on, `"false"` included.
+
+```html
+<!-- INCORRECT -->
+<mds-button disabled="false">Save</mds-button>
+
+<!-- CORRECT -->
+<mds-button>Save</mds-button>
+```
+
+Reported: the string `"false"` in any form, and an Angular attribute binding
+(`[attr.disabled]="false"`), which writes the attribute `"false"`. Bind a real boolean to the
+property instead: `<MdsButton disabled={isDisabled}>`, `[disabled]="isDisabled"`.
+
+### accessible-name
+
+A component that takes an `icon` next to a `label` or a default slot, shown with its icon
+alone, needs a name: without `label` or `aria-label`, `mds-button` is announced by the slug of
+its icon, which names the icon and not the action. An `mds-img` with a `src` and no `alt` is
+named after its file: describe the image, or set `alt=""` when it is decorative.
+
+```html
+<!-- INCORRECT -->
+<mds-button icon="mi/baseline/send"></mds-button>
+<mds-img src="/img/report-2024.jpg"></mds-img>
+
+<!-- CORRECT -->
+<mds-button icon="mi/baseline/send" label="Send"></mds-button>
+<mds-img src="/img/report-2024.jpg" alt="Annual report 2024"></mds-img>
+```
+
+Left alone, because one element does not show its name: an element with an `id` (an
+`mds-tooltip` with `relation="label"`, or an `aria-labelledby` elsewhere, may name it) and
+one that spreads its props (`{...props}`).
+
+### no-raw-palette-classes
+
+A colour class names a role ([`color.md`](color.md)), never Tailwind's palette (`bg-white`,
+`text-gray-700`), which ignores Magma, nor a raw Magma step (`bg-tone-neutral-03`,
+`border-surface-neutral-default`), which follows the mode only. Variants, `!` and opacity are
+read through: `dark:hover:bg-white/50` is `bg-white`.
+
+```html
+<!-- INCORRECT -->
+<section class="bg-white text-gray-700">...</section>
+
+<!-- CORRECT -->
+<section class="bg-surface-raised text-fg-default">...</section>
+```
+
+Not reported: `label-*` and `brand-*`, for colour that encodes data, and the seed of a tone,
+the pure extreme of the mode.
+
+A class is read wherever the project writes one, in the forms the codemod migrates:
+
+- the `class` attribute of HTML and Angular templates;
+- React: every string in a `className` (or `class`) expression, the arguments and object keys
+  of `clsx()` or `classnames()`, both branches of a ternary, a `||` fallback, and the fixed
+  parts of a template literal;
+- Angular: the key of `[class.<name>]` and the quoted strings of `[ngClass]`, `[class]` and
+  `[attr.class]`;
+- Stylelint: the classes of `@apply`.
+
+```tsx
+// INCORRECT
+<div className={clsx('p-400', active && 'bg-white')} />
+
+// CORRECT
+<div className={clsx('p-400', active && 'bg-surface-raised')} />
+```
+
+Not read: a class put together at run time (`bg-${tone}-03`, of which only the fixed parts are
+read), classes kept in a variable outside the attribute (`const card = clsx(...)`), and HTML
+written as a string in a script (`el.innerHTML = ...`). A string compared in a condition is
+read too, and reported only when it is itself a palette class.
+
+### no-color-scheme-override
+
+A `prefers-color-scheme` media query follows the OS, not the mode the user picked
+(`mds-pref-mode`). The roles follow both: paint with them, and dark mode comes with no
+query. For a deliberate choice that differs per mode, use the `dark` variant of the Magma
+Tailwind theme, which follows the Magma mode ([`theming.md`](theming.md)).
+
+```css
+/* INCORRECT */
+@media (prefers-color-scheme: dark) {
+  .panel {
+    background: rgb(var(--magma-surface-overlay));
+  }
+}
+
+/* CORRECT */
+.panel {
+  background: rgb(var(--magma-surface-raised));
+}
+```
+
+### no-raw-color
+
+A hex, `rgb()`, `hsl()`, `oklch()` or other colour literal where a role belongs. A colour that
+names a token is fine (`rgb(var(--magma-text-muted) / 0.5)`), and so are the keywords
+(`currentColor`, `transparent`). In a shadow the hint is the shadow ink,
+`rgb(var(--magma-shadow-ink) / <alpha>)`. Not read: `mask` and `mask-image`, and the
+`initial-value` of an `@property`.
+
+Not reported either: the public custom properties marked **Static** in a component's
+`AGENTS.md`, which take a colour of their own, not a role (the skin of an illustration, the
+cover of a book from its catalogue record):
+
+```css
+mds-emoji[name='simi'] {
+  --mds-emoji-simi-skin: #f5c8a0;
+}
+```
+
+Any other colour that is not a role keeps its literal under a disable comment that says why:
+`/* stylelint-disable-next-line magma/no-raw-color -- <the reason> */`.
+
+### no-internal-tokens
+
+An `--mds-*` custom property, set or read, that no component promises. A component's
+`AGENTS.md` lists its public custom properties, the only ones a product sets; the others are
+internal, its implementation, and may change or go in any release without notice. A name no
+component documents is reported too. Stylelint reads the stylesheets, the classes of `@apply`
+included; ESLint reads the inline styles of the templates (a `style` attribute, a React
+`style={{ '--mds-<name>': ... }}` object, an Angular `[style.--mds-<name>]` binding) and their
+Tailwind classes, wherever [`no-raw-palette-classes`](#no-raw-palette-classes) reads a class,
+through variants and `!`: an arbitrary property that sets one
+(`[--mds-<name>:<value>]`, on the component or on a parent that sets it for its descendants)
+and an arbitrary value that reads one (`bg-[var(--mds-<name>)]`, `bg-(--mds-<name>)`).
+
+```css
+/* INCORRECT: internal, it may change in any release */
+mds-chip {
+  --mds-chip-icon-color: rgb(var(--magma-accent-fg));
+}
+
+/* CORRECT: a public custom property of the chip */
+mds-chip {
+  --mds-chip-icon-background: rgb(var(--magma-accent-surface));
+}
+```
+
+When no public custom property does what you need, use a prop, a documented part, or a role
+on the markup around the component; if none does, ask for one ([`reporting.md`](reporting.md))
+rather than setting an internal one.
+
+## Settings
+
+The rules need no settings: they read the `documentation.json` beside them in the installed
+`magma`, and the tokens of the `design-tokens` and `styles` it depends on. To check against
+other files, set their paths under `settings.magma` in the ESLint configuration (relative to
+`root`, the project by default): `documentation`, `tokens`, `consumption`. The Stylelint rules
+take the paths they read as secondary options, `root` and `documentation` for `no-internal-tokens`
+and `no-raw-color`, `root`, `tokens` and `consumption` for `no-raw-palette-classes`:
+`'magma/no-internal-tokens': [true, { documentation: './documentation.json' }]`.

package/agents/mcp.md

@@ -0,0 +1,107 @@
+<!--
+  GENERATED FILE - do not edit by hand.
+  Source of truth: docs/agents/ in the magma monorepo.
+  Regenerate with: npm run sync.agent-docs (from the stencil package).
+-->
+# Magma MCP server
+
+> Scope: asking Magma precise questions while you work, through the MCP server that ships
+> inside `@maggioli-design-system/magma`. Set it up once, when you install Magma; then reach
+> for its tools instead of reading whole files.
+
+The server answers from the version installed in the project: the components and their
+API, the roles and tokens with what each one is for, the classes of the Magma Tailwind
+theme, the icon slugs that exist, the sections of these guides, and the lint
+([`lint.md`](lint.md)) on a snippet before it is written. It is read-only: no tool changes
+a file.
+
+## Set it up
+
+Nothing to install: the server is the `magma-mcp` command of `@maggioli-design-system/magma`,
+which `magma-react` and `magma-angular` require too. The agent's client starts it on stdio
+from the project's root; MERGE the entry into the client's configuration, never replace
+the file.
+
+### Claude Code: the Magma plugin
+
+In Claude Code, the Magma plugin starts the server for you and adds the skills that run a
+whole job: `/magma:setup`, `/magma:review`, `/magma:migrate`, and `ui`, which Claude loads by
+itself for UI work. Register it for the whole team in the project's committed
+`.claude/settings.json`; Claude Code loads it once the folder is trusted, in the terminal and
+in the desktop app, which reads the same settings:
+
+```json
+{
+  "extraKnownMarketplaces": {
+    "magma": { "source": { "source": "github", "repo": "magma-design-system/magma" }, "autoUpdate": true }
+  },
+  "enabledPlugins": { "magma@magma": true }
+}
+```
+
+On one machine only, in a Claude Code session in the terminal:
+`/plugin marketplace add magma-design-system/magma`, then `/plugin install magma@magma`.
+
+With the plugin, do not also add the `.mcp.json` entry below: the server would run twice.
+
+### Claude Code without the plugin, and the other clients
+
+Claude Code, `.mcp.json` at the project root (committed, so the whole team gets it; Claude
+Code asks once before it starts a project server):
+
+```json
+{
+  "mcpServers": {
+    "magma": { "command": "npx", "args": ["--no", "magma-mcp"] }
+  }
+}
+```
+
+VS Code (GitHub Copilot), `.vscode/mcp.json`:
+
+```json
+{
+  "servers": {
+    "magma": { "type": "stdio", "command": "npx", "args": ["--no", "magma-mcp"] }
+  }
+}
+```
+
+Cursor, `.cursor/mcp.json`: the same entry as Claude Code, under `mcpServers`.
+
+`npx --no magma-mcp` runs the installed version, so the answers always match the components
+the project uses. Keep `--no`: without it, a client that starts the server before
+`npm install` (a fresh clone with the configuration committed) lets `npx` download and run
+whatever package the npm registry has under that name; with it, `npx` stops instead. When the
+client starts servers elsewhere than the project's root, pass it:
+`"args": ["--no", "magma-mcp", "--root", "<the project's folder>"]`.
+
+## The tools
+
+| Tool | Ask it | Instead of |
+| --- | --- | --- |
+| `find_component` | which component fits a need ("a date range picker") | reading the catalogue |
+| `get_component` | the API of one component: props with their values and default, events, methods, slots, parts, public CSS custom properties | reading its `AGENTS.md` |
+| `get_usage` | how HTML, React or Angular writes it: import, props, events (`onMdsInputChange`, `(mdsInputChange)`) | guessing the names |
+| `list_tokens` | the role for a need ("secondary text"), with its value and class | reading [`color.md`](color.md) |
+| `suggest_role` | the role for a colour, a raw class or a palette step, as a class of the same utility (`shadow-*/80` stays a shadow class) | picking a role by eye |
+| `explain_class` | what a class does with the Magma theme | the trap of the scale: `p-4` is 0.01rem, `p-400` is 1rem |
+| `find_icon` | a slug that exists, by meaning, or whether a slug exists | an `icon="..."` that renders nothing |
+| `get_guide` | one section of a guide | reading the whole file |
+| `check_markup` | whether a snippet passes the lint, before it is written | a lint run after the fact |
+| `check_setup` | what the Magma integration of the project misses | checking the install steps by hand |
+
+`check_markup` uses the ESLint, Stylelint and template parsers the project installed with
+the lint ([`lint.md`](lint.md)). The same definitions, for a tool that documents them, are in
+`@maggioli-design-system/magma/dist/lint/mcp/tools.json`: what `tools/list` answers.
+
+## When to call them
+
+- Before writing a component: `find_component`, then `get_component` and `get_usage`.
+- Before a colour, a spacing or a class: `list_tokens`, `suggest_role`, `explain_class`.
+- Before an icon: `find_icon`.
+- After writing: `check_markup`, then the project's lint ([`lint.md`](lint.md)).
+- After the bootstrap, or when something does not render: `check_setup`.
+- When no tool gives you what the task needs, or an answer carries `gap`: tell the user,
+  and at the end of the task propose an issue on Magma
+  ([`reporting.md`](reporting.md), "A tool or an answer the MCP server is missing").

package/agents/reporting.md

@@ -7,8 +7,9 @@
 
 > Scope: you are working in a project that uses Magma and you hit a problem that is
 > Magma's, not the project's: a component that misbehaves, a guide that is wrong, a
-> missing token or utility, a packaging or install issue. This is how to report it to
-> the Magma repository, `magma-design-system/magma`, labelled with the project it comes
+> missing token or utility, a packaging or install issue, or something you needed that
+> the Magma MCP server does not answer (section 7). This is how to report it to the
+> Magma repository, `magma-design-system/magma`, labelled with the project it comes
 > from, so the maintainers can tell which project reported what.
 
 ## 1. Make sure it is Magma's
@@ -125,3 +126,53 @@ the title, the labels and the body to open it by hand at
 
 Then give the user the issue URL, and leave a comment in the project next to the
 workaround that links it, so the workaround can go once the fix ships.
+
+## 7. A tool or an answer the MCP server is missing
+
+The tools of the Magma MCP server ([`mcp.md`](mcp.md)) are there so you never read the
+installed files by hand or guess. When one of them could not give you what the task
+needed, Magma wants to know: the next tool or field comes from these reports. It is a gap
+when:
+
+- no tool covers the question, and you answered it by reading Magma's files
+  (`documentation.json`, the token data, the guides) or by guessing;
+- a tool said Magma has nothing for a well-formed question: its answer carries `gap`, or
+  its error says it does not know;
+- a tool answered, but not with what the task needed: a field it does not return, a
+  filter or an argument it does not take.
+
+It is not a gap when the answer is right but not the one you hoped for, when your own
+input was wrong (an unknown tag, a missing argument), or when the question is about the
+project rather than Magma.
+
+Tell the user when it happens, carry on with the task, and at the end propose one issue
+per missing capability, gathered from the whole task. Follow steps 2, 3, 4 and 6 (look
+for an existing issue, ask before opening it, the labels, create it), with `feature`,
+`prg-stencil` (the server ships inside `magma`) and the project's `prd-*` label, and this
+title and body instead of the ones of step 5. Title: `magma-mcp: <what is missing>`, e.g.
+`magma-mcp: find_component cannot filter by category`. Body:
+
+```markdown
+## Need
+
+What the task needed to know or to do, in one sentence.
+
+## What the server answered
+
+The tool you called and its arguments, and what it returned; or that no tool covers it.
+
+## What I did instead
+
+Read a file by hand, guessed, asked the user, and what it cost.
+
+## Proposal
+
+The tool, argument or field that would have answered it, if you have one in mind.
+
+## Versions
+
+- @maggioli-design-system/magma: <installed version>
+- Client: <e.g. Claude Code, VS Code, Cursor>
+
+Found in <project> (<repository>).
+```

package/agents/theming.md

@@ -28,6 +28,14 @@ let the user choose, each preference has its component - `mds-pref-mode`,
 `mds-pref-language` - and `mds-pref` groups them in one panel; they write the classes and
 remember the choice. Never write `color-scheme` or dark-mode media queries by hand.
 
+Tailwind's `dark:` follows the same mode: the Magma Tailwind theme brings a `dark`
+variant that turns on where the palette turns dark - `pref-mode-dark`, `pref-mode-system`
+or no controller on a dark OS, a theme locked to dark (`pref-theme-scheme-dark`) - and
+never under `pref-mode-light` or a theme locked to light (`pref-theme-scheme-light`). The
+roles flip without it, so `dark:` is never needed to correct a colour: use it only for a
+deliberate per-mode choice. It matches the light DOM only (pages, layouts, stories);
+inside a component's shadow root it matches nothing.
+
 ## Named themes
 
 A named theme retints the whole neutral scaffolding of the page at once - surfaces,

package/dist/components.js

@@ -15,6 +15,7 @@ export { MdsBadge } from "./mds-badge.js";
 export { MdsBanner } from "./mds-banner.js";
 export { MdsBenchmarkBar } from "./mds-benchmark-bar.js";
 export { MdsBibliography } from "./mds-bibliography.js";
+export { MdsBook } from "./mds-book.js";
 export { MdsBreadcrumbItem } from "./mds-breadcrumb-item.js";
 export { MdsBreadcrumb } from "./mds-breadcrumb.js";
 export { MdsButtonDropdown } from "./mds-button-dropdown.js";

package/dist/components.server.js

@@ -15,6 +15,7 @@ export { MdsBadge } from "./mds-badge.server.js";
 export { MdsBanner } from "./mds-banner.server.js";
 export { MdsBenchmarkBar } from "./mds-benchmark-bar.server.js";
 export { MdsBibliography } from "./mds-bibliography.server.js";
+export { MdsBook } from "./mds-book.server.js";
 export { MdsBreadcrumbItem } from "./mds-breadcrumb-item.server.js";
 export { MdsBreadcrumb } from "./mds-breadcrumb.server.js";
 export { MdsButtonDropdown } from "./mds-button-dropdown.server.js";

package/dist/mds-book.js

@@ -0,0 +1,12 @@
+'use client';
+import { createComponent } from '@stencil/react-output-target/runtime';
+import React from 'react';
+import { MdsBook as MdsBookElement, defineCustomElement as defineMdsBook } from "@maggioli-design-system/magma/dist/components/mds-book.js";
+export const MdsBook = /*@__PURE__*/ createComponent({
+    tagName: 'mds-book',
+    elementClass: MdsBookElement,
+    // @ts-ignore - ignore potential React type mismatches between the Stencil Output Target and your project.
+    react: React,
+    events: {},
+    defineCustomElement: defineMdsBook
+});

package/dist/mds-book.server.js

@@ -0,0 +1,23 @@
+'use client';
+import { createComponent } from '@stencil/react-output-target/ssr';
+// @ts-ignore - ignore potential type issues as the project is importing itself
+import * as clientComponents from "@maggioli-design-system/magma-react";
+export const serializeShadowRoot = "declarative-shadow-dom";
+export const MdsBook = /*@__PURE__*/ createComponent({
+    tagName: 'mds-book',
+    properties: {
+        alt: 'alt',
+        author: 'author',
+        binding: 'binding',
+        format: 'format',
+        loading: 'loading',
+        name: 'name',
+        pages: 'pages',
+        pose: 'pose',
+        publisher: 'publisher',
+        src: 'src'
+    },
+    hydrateModule: typeof window === 'undefined' ? import('@maggioli-design-system/magma/hydrate') : undefined,
+    clientModule: clientComponents.MdsBook,
+    serializeShadowRoot
+});

package/dist/types/components.d.ts

@@ -14,6 +14,7 @@ export { MdsBadge } from "./mds-badge.js";
 export { MdsBanner } from "./mds-banner.js";
 export { MdsBenchmarkBar } from "./mds-benchmark-bar.js";
 export { MdsBibliography } from "./mds-bibliography.js";
+export { MdsBook } from "./mds-book.js";
 export { MdsBreadcrumbItem } from "./mds-breadcrumb-item.js";
 export { MdsBreadcrumb } from "./mds-breadcrumb.js";
 export { MdsButtonDropdown } from "./mds-button-dropdown.js";

package/dist/types/components.server.d.ts

@@ -16,6 +16,7 @@ export { MdsBadge } from "./mds-badge.server.js";
 export { MdsBanner } from "./mds-banner.server.js";
 export { MdsBenchmarkBar } from "./mds-benchmark-bar.server.js";
 export { MdsBibliography } from "./mds-bibliography.server.js";
+export { MdsBook } from "./mds-book.server.js";
 export { MdsBreadcrumbItem } from "./mds-breadcrumb-item.server.js";
 export { MdsBreadcrumb } from "./mds-breadcrumb.server.js";
 export { MdsButtonDropdown } from "./mds-button-dropdown.server.js";

package/dist/types/mds-book.d.ts

@@ -0,0 +1,9 @@
+/**
+ * This file was automatically generated by the Stencil React Output Target.
+ * Changes to this file may cause incorrect behavior and will be lost if the code is regenerated.
+ */
+import type { StencilReactComponent } from '@stencil/react-output-target/runtime';
+import type { Components } from "@maggioli-design-system/magma/dist/components";
+import { MdsBook as MdsBookElement } from "@maggioli-design-system/magma/dist/components/mds-book.js";
+export type MdsBookEvents = NonNullable<unknown>;
+export declare const MdsBook: StencilReactComponent<MdsBookElement, MdsBookEvents, Components.MdsBook>;

package/dist/types/mds-book.server.d.ts

@@ -0,0 +1,11 @@
+/**
+ * This file was automatically generated by the Stencil React Output Target.
+ * Changes to this file may cause incorrect behavior and will be lost if the code is regenerated.
+ */
+import type { StencilReactComponent } from '@stencil/react-output-target/runtime';
+import { type SerializeShadowRootOptions } from '@stencil/react-output-target/ssr';
+import type { Components } from "@maggioli-design-system/magma/dist/components";
+import { MdsBook as MdsBookElement } from "@maggioli-design-system/magma/dist/components/mds-book.js";
+export declare const serializeShadowRoot: SerializeShadowRootOptions;
+export type MdsBookEvents = NonNullable<unknown>;
+export declare const MdsBook: StencilReactComponent<MdsBookElement, MdsBookEvents, Components.MdsBook>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maggioli-design-system/magma-react",
-  "version": "2.5.1",
+  "version": "2.7.0",
   "license": "MIT",
   "main": "dist/components.js",
   "module": "dist/components.js",
@@ -35,7 +35,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@maggioli-design-system/magma": "2.5.1",
+    "@maggioli-design-system/magma": "2.7.0",
     "@stencil/react-output-target": "1.6.5"
   },
   "repository": {