NextViper Error Code Registry
Every diagnostic emitted by the NextViper compiler, runtime, package manager, and CLI includes a stable, machine-readable error code. Select an error code below for in-depth root causes, code examples, and verified fixes.
Compiler Errors
5 codesUnknown Identifier
The compiler encountered an identifier, variable, or function name that has not been declared or is not in scope.
Syntax Error
The source code violates NextViper grammatical syntax rules and cannot be parsed into an Abstract Syntax Tree (AST).
Type Mismatch
An expression evaluates to a type incompatible with the expected destination type or operator operand requirements.
Invalid Function Call
A function or method was invoked with an incorrect number of arguments or incompatible argument types.
Module Not Found
The compiler cannot find the requested standard library module or local source file.
CLI Errors
2 codesPackage Manager Errors
3 codesPackage Not Found
A declared dependency package is not installed locally in .nextviper/packages or cannot be found in the registry.
Dependency Resolution Error
The package manager failed to solve a compatible set of package versions satisfying all SemVer constraints.
Package Integrity Checksum Mismatch
The cryptographic SHA-256 hash of a downloaded package does not match the checksum recorded in nextviper.lock.
Runtime Errors
5 codesDivision by Zero
The program attempted to divide an integer or float by zero during execution.
Index Out of Bounds
An indexing operation requested an element index outside the valid range [0, length - 1] of a list, array, or string.
Key Not Found
An access operation on a map/dictionary requested a key that does not exist.
Null Reference
An operation or method call was executed on a 'null' or 'nil' value.
File I/O Error
A runtime standard library filesystem operation failed during read, write, or creation.