import React from 'react'; /** * The page builder's drop seam. `Area.tsx` owns every instance: one as the * first child of each Area marked `editableInPageBuilder` * (`variant="start"`), and one after every renderable in such an Area — * widget instances and layout components alike. That makes each gap in the * rendered order a drop target: above everything, between any two * renderables (widget-widget, widget-layout, layout-layout), and below the * last one. * * Visibility and styling come from the `[data-evershop-pb-dropzone]` rules * in the chrome stylesheet (`ensureChromeStyleInjected` in * `WidgetChrome.tsx`, guaranteed by `PageBuilderBridge` even on routes with * zero widgets): zones are zero-height and inert until the admin posts * `pb-drag-start`, which sets `body[data-evershop-pb-drag="true"]`. * * The drop handler walks DOM siblings to find the nearest renderables' * `data-evershop-pb-sort-order` and computes a midpoint locally — see * `dropSortOrder.ts`. The admin just stores the computed value. * * SSR-safe: returns `null` outside the page-builder iframe so the production * storefront emits zero extra DOM. */ interface AreaDropZoneProps { areaId: string; /** * 'start' — the zone above everything in the area (Area's first child), * tagged `data-evershop-pb-area-start` for e2e / debugging. * 'after' (default) — the zone following one renderable. */ variant?: 'start' | 'after'; /** * uuid of the widget instance this zone follows, when it follows one. * Surfaced as `data-evershop-pb-after` — an e2e / debugging hook only; * the drop math never reads it. Zones after layout components have no * uuid and omit the attribute. */ afterUid?: string; } export declare function AreaDropZone({ areaId, variant, afterUid }: AreaDropZoneProps): React.ReactElement | null; export {};