Skip to content
Shopware

Try It Out

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.

1. Choose a template

2. Choose an environment

LaunchingVue Starter TemplateinLocal clone
npx tiged shopware/frontends/templates/vue-starter-template my-store && cd my-store && npm install && npm run dev

Or: delegate to an AI agent

Paste this prompt into Claude, Cursor, Copilot, or any code assistant. The prompt is tailored to Vue Starter Template.

I want to set up the Shopware Frontends Vue Starter Template for local development.

In my current working directory, please:

1. Run `npx tiged shopware/frontends/templates/vue-starter-template my-store`
2. `cd my-store`
3. Run `npm install`
4. Start the dev server with `npm run dev` and tell me when it's ready on http://localhost:3000

If anything fails, surface the error and stop — don't try to "fix" peer-dep warnings unless I ask.

The template is Nuxt 4 + UnoCSS + the Shopware composables/cms-base layers, pre-configured against a public demo backend. After it's running, point me at `app/` for components and pages, and `nuxt.config.ts` for runtime configuration.

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, then pnpm 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