VERTICAL CONTEXTS

Rules

• Import only the hook, from the specifier listed here. The specifier is the package path, such as @wix/stores/context/product. Never guess one; copy it from the vertical’s file.
• A hook works only inside the area that provides its context — a page the business solution sets up, a Data Source the Wix user attached, or an item in a list. Anywhere else it throws (see When the Hook Throws).
• Connecting an element to business-solution data (“bind the slider’s items to my store products”) means reading the vertical’s hook (@wix/stores/context/product-list for a product list). Never fetch it with the Wix SDK (productsV3.queryProducts(), posts.queryPosts()) in a provider or component: Manage Data and Manage Items work only on a context or Data Source, so an SDK fetch makes Manage Data open Code Mode, Manage Items do nothing, and the element render empty.
• Consume it in an Editor React component or in a provider you write, as in Importing a Context in Code. A native element reads the vertical’s values through Editor Binding instead.
• The business solution must be installed on the site (Wix Stores for @wix/stores/...). Check the site’s installed apps first. If the solution is missing, tell the user to install it and stop. If the platform rejects the code with Missing dependencies: <id> (@wix/stores/context/<name>) for app <id>, do not retry, rewrite or delete the context: name the missing dependency in your final message.
• A specifier exists only from the package version that added it. Before importing, make sure package.json and node_modules/@wix/<vertical> are on the latest version (npm install @wix/<vertical>@latest), and confirm: grep '"./context/<name>"' node_modules/@wix/<vertical>/package.json. Never put // @ts-ignore above these imports. TS2307 Cannot find module '@wix/<vertical>/context/<name>' means the package is too old: upgrade it, never fall back to an SDK fetch.
• Blog renamed post-item to post-list-item (hook usePostListItemContext) by @wix/blog 1.0.708, and added post-by-slug, whose usePostBySlugContext returns the same properties as usePostContext. Use the new names.
• A hook listed with optional: true also has a no-argument form. The package’s own examples call useServiceContext(), which returns the value and throws outside its area; optional: true returns null instead. Read the installed .d.ts for the exact overloads.
• If the vertical’s context already holds the field, do not add a settings panel, a data field or an SDK call to collect it again.

Index