Where the SDK types actually live
A Wix vertical package such as @wix/ecom is a thin re-export barrel. build/es/index.d.mts is a
list of namespaces (orders, orderTransactions, currentCart, …), each re-exported from its own
generated package:
node_modules/@wix/ecom/build/es/index.d.mts # namespace list only, ~90 lines
node_modules/@wix/auto_sdk_ecom_orders/build/es/
index.d.mts # the callable functions
index.typings.d.mts # request/response types
ecom-v1-order-orders.universal-<hash>.d.mts # the domain entitiesThree consequences:
- The directory name is not the namespace name.
extendedBookingslives inauto_sdk_bookings_extended-bookings. Don't derive one from the other; the SDK lookup maps them. - The entity is not always in
index.typings.d.mts.Order,Refund,Servicelive in the hashed*.universal-*.d.mtswhen the package has one. The hash changes between versions, so glob for it, never hard-code it, and fall back toindex.typings.d.mtswhen no universal file exists. - Never
cator plain-grepthe barrel's export block. These files end with a single several-hundred-KBexport { … as a, … as b }line, sogrep -n "queryServices" index.d.mtsprints that whole line. Anchor to the declarations instead —grep -oE "^declare (const|function) [a-zA-Z]+"— or pipe any barrel grep throughcut -c1-200.