Try It Out
Pick a template and an environment to launch a working storefront. The whole flow is read-only friendly — feel free to look around before you change anything.
What to expect during boot
- The dev server starts on port
3000. The environments above auto-forward it; once it's ready, the preview opens automatically. - First boot is slower than subsequent boots. Cold installs fetch the workspace, run
pnpm install, thenpnpm run dev. - Some warnings are normal. They don't block startup. See the FAQ below if a warning looks alarming.
Known warnings (safe to ignore)
EBADENGINE / Node engine warnings
Some packages declare a Node engines range stricter than the sandbox provides. The starter is tested against Node 22 and runs fine; the warning is informational. We're tracking #2360 to silence these on first run.
Peer dependency warnings (@tresjs/core / @tresjs/cientos)
These appear in some package-manager combinations. They don't affect the storefront — 3D content lazy-loads only when CMS pages opt into the spatial viewer. Tracked in #2360.
Deprecation warnings on first install
A few transitive dependencies emit deprecation warnings. They're upstream and will be cleared as we bump dependency versions. Not a blocker.
After it's ready
Once the preview is up:
- The home page should render — that confirms the storefront is wired correctly to the demo Shopware backend.
- Navigate into a category or a product to see CMS-driven content.
- Open
app/in the editor for components and pages — that's where your customizations live.
Vue Starter Template — full guide
Production-ready foundation for custom storefronts
Vue Starter Template Extended — full guide
Branded demo built with Nuxt layers on top of the starter