Is there a way to access arbitrary node data inside MiniMap nodeComponent prop? #5430

Checked this against the MiniMap source (MiniMapNodes.tsx/types.ts), and no, there's currently no way to get data into nodeComponent. MiniMapNodeProps is a fixed shape (id, x, y, width, height, borderRadius, className, color, strokeColor, strokeWidth, style, selected), it doesn't include data. Internally, NodeComponentWrapper does pull the full user node (including data) from the store, but only to feed it into nodeColor/nodeStrokeColor/nodeClassName, whatever those functions return is what actually reaches your nodeComponent, the raw node itself never gets forwarded.

So your workaround isn't really a workaround, it's the intended mechanism, nodeColor, nodeStrokeColor and nodeClassName are literally the only three props typed as (node: Node) => string, i.e. the only channels that receive the full node. Since you have three of them and currently only using one, you don't need to overload color with your active/inactive logic:

<MiniMap
  nodeColor={(node) => node.data.active ? 'blue' : 'transparent'}
  nodeStrokeColor={(node) => node.data.active ? 'transparent' : 'blue'}
  nodeComponent={({ x, y, color, strokeColor }) => (
    <circle r={50} fill={color} stroke={strokeColor} strokeWidth={10} cx={x} cy={y} />
  )}
/>

That mirrors exactly what your current code does through a single nodeColor function, just split across the two props that already exist for fill vs stroke, which reads a bit more directly than branching inside nodeComponent on one merged color value. If you ever need more than color/stroke/class worth of data inside the custom shape (say, a label or a numeric value driving radius), nodeClassName is still free as a third channel, you could encode a value into a class name and read it back via a CSS variable, though at that point you're pushing the string-encoding trick about as far as it goes and it might be worth opening a feature request for a data-passthrough prop on nodeComponent directly.