@mittwald/flow-react-components 1.2.0-next.49 → 1.2.0-next.50

package/MIGRATION.md

@@ -28,6 +28,45 @@ The CLI's own output does detect it and prints the right form.
 
 ---
 
+<a id="tabler-icons-no-longer-transitive"></a>
+
+## @tabler/icons-react is no longer installed alongside Flow
+
+**Since `1.1.40`** · migration · manual change · also applies to
+`@mittwald/flow-remote-react-components`
+
+Flow no longer depends on `@tabler/icons-react`. `@mittwald/flow-icons` carries
+the path data of the 123 icons it uses directly, so a Flow install stops pulling
+in 74 MB and ~24,000 files it never needed.
+
+The icons themselves do not change: same names, same exports, same rendered
+`<svg>` including the `tabler-icon` and `tabler-icon-<name>` classes.
+
+The one thing that breaks is code which imported `@tabler/icons-react` without
+declaring it, and got it because npm hoisted Flow's copy into the project's
+`node_modules`. That copy is gone. Declare the package where you use it:
+
+```shell
+npm i @tabler/icons-react
+```
+
+```tsx
+// unchanged — it just needs the package in your own dependencies now
+import { IconStar } from "@tabler/icons-react";
+
+<Icon>
+  <IconStar />
+</Icon>;
+```
+
+**Apply:** Only affects code that imports from `@tabler/icons-react` — typically
+a `<Icon><IconSomething /></Icon>` using an icon that is not in Flow's own set.
+Add the package to your own dependencies (`npm i @tabler/icons-react`); the
+imports themselves stay unchanged. Flow's own `Icon*` components are unaffected,
+keep their names, and render exactly as before.
+
+---
+
 <a id="option-value-inferred-from-mixed-children"></a>
 
 ## Option: value is inferred from mixed children