fix(deps): update dependency @sanity/icons to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@sanity/icons (source)	^3.7.4 → ^5.0.0

---

Release Notes

sanity-io/ui (@​sanity/icons)

v5.2.1

Patch Changes

• #​2418 18c0323 Thanks @​stipsan! - @sanity/icons is now developed in the sanity-io/ui monorepo (packages/icons), with full git history preserved. No runtime changes.

v5.2.0

Minor Changes

• #​234 6dae460 Thanks @​stipsan! - Restore React 18 support.

  Icon components (and the Icon wrapper) are wrapped in React.forwardRef again, so refs attach to the underlying svg element on React 18 as well as React 19. The react peer dependency range is widened from ^19 to ^18 || ^19, and the Node.js engines range from >=22.12 to >=20.19 <22 || >=22.12, matching @sanity/ui.

v5.1.0

Minor Changes

• #​223 e5657d5 Thanks @​stipsan! - Importing an icon from the root entry now resolves in the type system to a @deprecated never-typed tombstone instead of failing with a bare "has no exported member" error. Since v5 removed the per-icon barrel exports, import {RocketIcon} from '@sanity/icons' was indistinguishable from the icon having been deleted; the tombstone's deprecation message now points at the subpath the icon lives on, e.g. import {RocketIcon} from '@sanity/icons/Rocket'. The tombstones are declaration-only (export declare const RocketIcon: never), so nothing changes at runtime: the root entry still ships no icon code and bundlers/Node.js still reject root icon imports.

v5.0.0

Major Changes

• #​215 19689cc Thanks @​stipsan! - The deprecated per-icon barrel exports are removed: import {RocketIcon} from '@sanity/icons' no longer works, import icons from their own export path instead, e.g. import {RocketIcon} from '@sanity/icons/Rocket'. The root entry now only exposes the dynamic pieces – the <Icon> component, the icons map, and their types – and every entry in the icons map is built with React.lazy, so importing the root entry no longer pulls the full icon set into your bundle: each icon loads as its own chunk the first time it renders. <Icon> wraps the lazy icon in a <Suspense> boundary whose fallback is an svg with the same shell (viewBox, width/height and spread props) as the icon it is loading, so the slot reserves its final size and responds to the same styling while the chunk loads – the way an <img> with intrinsic dimensions behaves. When rendering components from the icons map directly, provide your own <Suspense> boundary.

v4.1.0

Minor Changes

• #​182 e7538d4 Thanks @​stipsan! - Every icon is now available on its own export path, e.g. import {RocketIcon} from '@sanity/icons/Rocket', letting userland opt in to smaller bundles and faster treeshaking. Each subpath exposes the icon both as a named export (identical to the barrel export) and as the default export, so React.lazy(() => import('@sanity/icons/Rocket')) works out of the box. Importing individual icons from the root barrel (import {RocketIcon} from '@sanity/icons') still works but is now marked @deprecated, pointing to the per-icon subpath to avoid barrel file performance issues.

v4.0.0

Major Changes

• #​200 26b9248 Thanks @​stipsan! - Drop CommonJS support and require Node.js >=22.12

  @sanity/icons is now ESM-only. The require export condition and the CommonJS build output (./dist/index.cjs) have been removed, so the package must be consumed via ESM import. The minimum supported Node.js version has been raised to >=22.12 to match sanity.

• #​201 01e3807 Thanks @​stipsan! - Drop React 18 support — React 19 is now required.

  Icon components no longer use forwardRef. Refs are now accepted as a regular prop (typed via React.ComponentPropsWithRef), following React 19's ref-as-prop model. The react peer dependency range is now ^19, and the exported IconComponent type has changed accordingly.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website	Ready	Preview	Aug 10, 2026 5:27am