Internals inspector
Run an expression through the library and inspect the parser stages and object structure that sit behind the final result. This page uses the same browser bundle as the Playground and Showcase.
——From source to object
The first two stages come from the internal parser instance exposed by the compatibility registry. The final result uses the normal nerdamer(...) entry point.
————nerdamer/debug subpath. Until a browser debug artifact is wired into this page, token and RPN inspection uses the exposed parser instance directly. That means bracketless-function preprocessing performed inside Parser.parse() is not represented in the token/RPN panels.Tokens
Tokenization identifies numbers, variables, functions, operators, and nested scopes. Hover a token to see its source position when one is available.
Reverse Polish notation
RPN encodes operator precedence by order. The parser can then evaluate the sequence with a stack rather than repeatedly resolving infix precedence.
Parser entity structure
ParserEntity is the outer runtime family, not one expression-node shape. A result can be an Expression, Equation, Vector, Matrix, ValuesSet, Collection, or Dictionary. Expression nodes then have their own group/type plus multiplier, power, base, elements, and function arguments.
typeName is the expression group such as SUM or PRD; multiplier stores the coefficient; power and base are shown as child expressions when present; elements and args hold the remaining symbolic children. Structured parser entities expose their rows, sides, entries, or elements instead.