This store theme exists to exercise and validate delivery-promise-components (vtex.delivery-promise-components) in a real Store Framework setup.
Account requirement: it is only expected to work in VTEX accounts where delivery promise components are enabled (and any related platform capabilities your team uses for delivery promises). On accounts without that support, blocks and APIs this theme relies on may be missing or behave differently.
Helper script in the repository root (same folder as manifest.json) to prepare a non-master development workspace and link this theme.
- VTEX IO CLI installed and logged in (
vtex login). jqinstalled (used to setvendorinmanifest.json).- Run the script from the theme root so
./manifest.jsonis found.
vtex switch my_account
cd /path/to/delivery-promise-theme
chmod +x ./setup-workspace.sh # once
./setup-workspace.shThe script will:
- Read the account from
vtex whoamiand ask you to confirm before continuing. - Ask for a workspace name (lowercase letters only;
masteris not allowed). - Run
vtex workspace use <name>, answering yes if the CLI offers to create the workspace. - Warn that the workspace will be reset and ask for your explicit permission; if you agree, it runs
vtex workspace reset(and confirms the CLI prompt). - Install
vtex.search-session@0.x. - Set
manifest.jsonvendorto the detected account name. - Ask which header layout to use and patch
store/blocks/header/header.jsonc: case1 (shopper-location-setter only), case2 (+ pickup-point-selector), or case3 (+ shipping-method-selector). This updates the sticky header row references for desktop and mobile. - Run
vtex link --no-watch. - Run
vtex lsand uninstall every app whose vendor equals your account (confirming each uninstall prompt), except the linked store theme (vendor.namefrommanifest.json, e.g.account.delivery-promise-theme). PUTstore/routes.jsonon vbase for Pages GraphQL user data, usingvtex local tokenasVtexIdclientAutCookie.- Run
vtex browseto open the workspace in the browser.
If any step fails (empty token, missing manifest.json, etc.), the script exits with an error message.