|
| 1 | +--- |
| 2 | +'@object-ui/app-shell': patch |
| 3 | +'@object-ui/cli': patch |
| 4 | +'@object-ui/components': patch |
| 5 | +'@object-ui/console': patch |
| 6 | +'@object-ui/fields': patch |
| 7 | +'@object-ui/layout': patch |
| 8 | +'@object-ui/plugin-ai': patch |
| 9 | +'@object-ui/plugin-calendar': patch |
| 10 | +'@object-ui/plugin-charts': patch |
| 11 | +'@object-ui/plugin-chatbot': patch |
| 12 | +'@object-ui/plugin-dashboard': patch |
| 13 | +'@object-ui/plugin-designer': patch |
| 14 | +'@object-ui/plugin-detail': patch |
| 15 | +'@object-ui/plugin-form': patch |
| 16 | +'@object-ui/plugin-gantt': patch |
| 17 | +'@object-ui/plugin-grid': patch |
| 18 | +'@object-ui/plugin-kanban': patch |
| 19 | +'@object-ui/plugin-list': patch |
| 20 | +'@object-ui/plugin-report': patch |
| 21 | +'@object-ui/plugin-tree': patch |
| 22 | +'@object-ui/plugin-view': patch |
| 23 | +'@object-ui/runner': patch |
| 24 | +'@object-ui/types': patch |
| 25 | +--- |
| 26 | + |
| 27 | +Move `lucide-react` from `^1.31.0` to `^1.43.0` in every package that declares it, and |
| 28 | +repair what the jump breaks, so icons resolved from a STRING keep drawing a glyph. |
| 29 | + |
| 30 | +Measured once against the installed 1.43.0 artifact when this change was made; nothing in |
| 31 | +the repository re-derives these readings. Across the jump lucide removes no runtime export, |
| 32 | +no public type name and no `lucide-react/dynamic.mjs` name, and every name this repository |
| 33 | +imports from `lucide-react` resolves. Exactly one key leaves the runtime `icons` record: |
| 34 | +`Trash2`, retired in favour of `trash`. |
| 35 | + |
| 36 | +What a user sees change: |
| 37 | + |
| 38 | +- Icons the lazy icon seam draws (`resolveIcon`, objectui#9251) get their path data again. |
| 39 | + lucide 1.43.0 icon modules export their path data inside `__iconData` and no longer |
| 40 | + export `__iconNode`; the seam now reads both. Reading only `__iconNode` against 1.43.0 |
| 41 | + leaves every such glyph an empty box, with nothing thrown or logged. |
| 42 | +- `DetailView`'s delete action and three schema-catalog examples spell their icon |
| 43 | + `trash`, not `trash-2`, so they keep resolving. The glyph is unchanged: 1.43.0's `trash` |
| 44 | + path data is byte-identical to the `trash-2` path data of 1.31.0 and 1.35.0. Anything |
| 45 | + that already authored `trash` now draws that same artwork, because lucide moved it under |
| 46 | + the `trash` name; a few other glyphs were also redrawn upstream. |
| 47 | +- Icons imported as COMPONENTS carry lucide 1.43.0's own classes: one class per declared |
| 48 | + alias (a spinner renders `class="lucide lucide-loader-circle lucide-loader-2 ..."`), and |
| 49 | + no longer the class lucide used to derive from the PascalCase key where that differs |
| 50 | + (`ArrowDown01` no longer carries `lucide-arrow-down01`). The canonical |
| 51 | + `lucide-<icon name>` class is still there, so a `.lucide-loader-circle` selector still |
| 52 | + matches. |
| 53 | +- Icons resolved from a STRING through the seam keep the classes they had: `lucide`, the |
| 54 | + canonical `lucide-<icon name>` class and the key-derived class. They do not carry |
| 55 | + lucide's per-alias classes. That is a maintainer ruling (objectui#8941, option C): the |
| 56 | + alias list lives only inside each lazily loaded icon module, and it was not moved into |
| 57 | + the eager name list. A selector that targets an alias class matches a component-imported |
| 58 | + icon and not a string-resolved one. This also dates the example in the objectui#9251 |
| 59 | + entry: `trash-2` no longer resolves as a string, so no seam-drawn glyph carries |
| 60 | + `lucide-trash2 lucide-trash-2`; a digit-bearing name that still resolves, such as |
| 61 | + `arrow-down-0-1`, carries `lucide-arrow-down01 lucide-arrow-down-0-1`. |
0 commit comments