love-ecommerce-template 1.0.0 · SDK 1.2.0

Validation

The validator checks a template against how the application treats it. Every rule corresponds to something the loader, renderer, sanitizers or storefront engine actually does; there are no general "best practice" rules.

SeverityMeaning
errorThe application will not load or render this correctly.
warningThe application changes or ignores something you wrote.
infoWorth knowing (unused keys and files, optional features).
node sdk validate [dir]          # human-readable
node sdk validate --json         # machine-readable: { ok, summary, diagnostics[] }

Exit code 1 when there are errors. The Studio validates continuously (only changed files are re-checked).

Rules

62 rules, read from lib/validate.js.

SeverityCodeMessage
errorasset-missing… does not exist in image/.
errorcss-relative-urlurl(…) resolves against /templates/<name>/…, which the application does not serve. Use an absolute /image/… path.
errordirective-errorTemplate engine:
errordirective-unbalancedTemplate engine:
errorjs-syntaxJavaScript syntax error:
errorjson-invalidtemplate.json is not valid JSON:
errorjson-typetemplate.json must contain a JSON object.
errormissing-file… is missing.
errorname-invalidInstall name "…" is not allowed by the application (…).
errorunsupported-script<script> elements are removed by the application. Put JavaScript in script.js.
errorunsupported-style<style> elements are removed by the application. Put CSS in styles.css.
warningaction-unknowndata-action="…" is not handled by the storefront engine (handle it in script.js).
warningarray-too-long… … has … items; the application uses the first ….
warningasset-large… is … MB. Large images slow the storefront down.
warningasset-not-served… will not be served: the application only serves … files from image/ (no hidden files).
warningcss-ambiguousBoth style.css and styles.css exist. The page links /style.css, which serves style.css, so styles.css is ignored by the storefront page.
warningcss-behaviorbehavior: is removed by the application.
warningcss-binding-moz-binding: is removed by the application.
warningcss-expressionexpression() is removed by the application.
warningcss-external-urlurl(…) is replaced with "none" by the application (no external URLs in CSS).
warningcss-import-removed@import is removed by the application. Combine the CSS into this file; for fonts use template.json assets.fonts.
warningcss-sanitizedThe application changes parts of this stylesheet when serving it (sanitizeCss).
warningcss-scroll-behaviorThe application's CSS sanitizer removes every "behavior:" declaration, which also breaks "scroll-behavior:" (it is served as a dangling "scroll-"). Set smooth scrolling from script.js instead, e.g. document.documentElement.style.scrollBehavior = "smooth".
warningdirective-unknown-data<!-- … … -->: "…" is not provided by the application (always empty/false).
warningduplicate-idid="…" is used more than once; the engine only finds the first.
warningfeature-incomplete… is present but … element(s) the engine uses with it are missing: …. All … installed templates that implement … have them.
warningfont-not-installed… …: font "…" is not installed in the application (available: …). It is ignored.
warningform-action-removedCross-origin form actions are removed by the application (forms may only post to the store itself).
warninggenerated-hook#… is created by the storefront engine; defining it in the template causes duplicates.
warninghead-removedEverything inside <head> is discarded by the application (title, meta, links). The application writes its own head.
warningimg-relativesrc="…" is relative to the page URL and will not find a template file. Use image/… or /image/….
warningitem-dropped… …[…] has no "…", so the application drops this item.
warningjs-sanitizedThe application rewrites this line when serving script.js (… is not allowed), so it will not work as written.
warningjson-wrong-type… labels.… should be a string.
warningno-home-sectionThere is no #section-home: unknown routes fall back to "home", so the page would show no section.
warningnumber-range… … should be ≥ ….
warningroute-unknown…="…" is not a storefront route (…); the engine shows the home page instead.
warningsection-missing…="…" links to a route this template does not implement (no #section-…); the engine shows the home page.
warningstyle-attr-removedstyle attributes containing external url() are removed by the application.
warningtoken-out-of-scope{…} only has a value inside a … block; here it stays as literal text.
warningtoken-unknown{…} is not a placeholder the application provides, so it appears literally on the page.
warningunsafe-url…="……" is replaced with "#" by the application.
warningunsupported-attrsrcdoc is removed by the application.
warningunsupported-event-attr…="…" is removed by the application. Bind events in script.js (or use data-action / data-nav).
warningunsupported-script<script type="
warningunsupported-tag<…> elements are removed by the application.
warningvalue-ignored… … "…" does not match …, so the application ignores it.
warningvalue-sanitized… … contains markup/script text that the application removes.
warningvalue-truncated… … is … characters; the application cuts it to ….
infoasset-unreferenced… is not referenced by index.html, styles.css, script.js or template.json (it is still served at … and listed in {TEMPLATE_IMAGES} when it is directly inside image/).
infodocument-tag<…> tags are removed; your markup becomes the content of the page body built by the application.
infofile-not-served… is not used by the application… and is left out of builds.
infofile-not-used… is loaded by the template engine but never rendered or served (only index.html, styles.css/style.css and script.js are used).
infoimg-no-src<img> without src.
infoimg-proxiedExternal image … is loaded through the application's image proxy (/img-proxy). Prefer files in image/.
infojs-no-themescript.js does not set window.StorefrontTheme (optional: labels, icons, colour and hooks for the storefront engine).
infokey-not-read… …: …
infokey-unknown… … is not read by the application.
infolabel-unknown… labels.… is not a word the engine uses (known: …).
inforaw-token{{{…}}} prints the value without HTML escaping (the page is sanitized afterwards).
infostore-token{…} is empty until a store is selected (and when the store has no value). Wrap it in <!-- IF … -->…<!-- ENDIF --> to avoid empty markup.
infoversion-mismatchtheme.json version (…) and template.json version (…) differ; the application reports theme.json's.
Generated 2026-10-01 11:59 UTC from the application source (contract 7075c14c24bbaf06).