Error codes

Summit writes its diagnostics so that a person or an AI agent can fix the problem on the next try. Each message carries a stable code, a plain-language cause, a hint when one fits, the offending expression and element, and a link to the docs page for the directive involved.

#Message format

Warnings go to console.warn and failures to console.error. Every message starts with the literal [summit] prefix, so tooling that searches for it keeps working.

[summit] E201: unknown directive "s-modle".
  Did you mean "s-model"?
  element: <input#email>
  docs: https://github.com/velofy/summitjs/blob/main/content/s-model.md

The lines are:

• [summit] CODE: message, always present.
• A hint line, when Summit has a suggestion or a fix.
• expression: with the failing expression, when there is one.
• element: with the tag, id, and up to two classes of the element involved.
• docs: with a link to the most relevant page.

When the problem was a thrown error, the original error is logged after the formatted message.

For an unknown directive, Summit compares the name against every registered directive and suggests the closest one within a small edit distance. The same unknown name is reported only once, so a repeated typo does not flood the console.

#Codes

#Details

#E101 and E102

The component's init() or destroy() method threw. Summit logs the thrown error after the message. See s-data and Lifecycle.

#E103

A store registered with Summit.store has an init() method that threw. See Summit.store.

#E104

The s-data expression could not be evaluated, for example because the object uses syntax the interpreter does not support, such as an async method. The component starts with empty state, and the rest of the page still initializes. See s-data.

#E201

An s-* attribute names a directive that nothing handles. (@* and :* attributes always go to s-on and s-bind.) When a close match exists, the hint reads Did you mean "s-..."? and the docs link points at that directive. Otherwise the link points at Getting Started.

#E301

A directive or an s-on handler threw while evaluating its expression. The hint is a reminder that every name in the expression must be state from an enclosing s-data, a $ magic, or an allowed global. See The CSP-safe evaluator. The docs link names the directive's own page, so for a directive you registered yourself it points at a page that does not exist.

#E401 and E402

s-for must sit on a <template> element, and that template needs exactly one root element. E402 fires when the template has no element inside it; Summit repeats only the first element child. See s-for.

#E501 and E502

s-teleport must sit on a <template> element, and its value must be a selector that matches an element in the document. See s-teleport.

#E601 and E602

A cleanup callback or a destroy() callback threw while an element was being removed. See Lifecycle.

#Messages without a code

The optional data layer prints two plain warnings:

• [summit] summit-net.min.js must load after summit.min.js. The CDN build of summitjs/net could not find window.Summit. Load the core script first.
• [summit] s-resource needs a name An s-resource directive was used without a name, as in s-resource="..." instead of s-resource:users="...". See Data Fetching.