jssm 5.157.1 → 5.157.3

package/README.md

@@ -18,10 +18,10 @@ Please edit the file it's derived from, instead: `./src/md/readme_base.md`
 
 
 
-* Generated for version 5.157.1 at 7/2/2026, 1:36:48 AM
+* Generated for version 5.157.3 at 7/2/2026, 7:29:57 AM
 
 -->
-# jssm 5.157.1
+# jssm 5.157.3
 
 [**Try the live editor**](https://stonecypher.github.io/jssm-viz-demo/graph_explorer.html) ·
 [Documentation](https://stonecypher.github.io/jssm/docs/) ·
@@ -312,7 +312,7 @@ That decision shows up everywhere downstream:
   or run `npm run benny` against your own machine.
 
 - **More thoroughly tested than any other JavaScript state-machine
-  library.**  7,866 tests at 100.0% line coverage
+  library.**  7,870 tests at 100.0% line coverage
   ([report](https://coveralls.io/github/StoneCypher/jssm)), plus
   fuzz testing via `fast-check`, with parser test data across ten natural
   languages and Emoji.
@@ -445,11 +445,11 @@ If your contribution is missing here, please open an issue.
 
 <br/>
 
-***7,866 tests***, run 82,908 times.
+***7,870 tests***, run 82,912 times.
 
-- 7,108 specs with 100.0% coverage
-- 758 fuzz tests with 53.5% coverage
-- 9,879 TypeScript lines - 0.8 tests per line, 8.4 generated tests per line
+- 7,112 specs with 100.0% coverage
+- 758 fuzz tests with 52.9% coverage
+- 9,969 TypeScript lines - 0.8 tests per line, 8.3 generated tests per line
 
 [![Actions Status](https://github.com/StoneCypher/jssm/workflows/Node%20CI/badge.svg)](https://github.com/StoneCypher/jssm/actions)
 [![NPM version](https://img.shields.io/npm/v/jssm.svg)](https://www.npmjs.com/package/jssm)

package/dist/cdn/instance.js

@@ -22750,6 +22750,12 @@ function fold_graph_config(aliases, explicit_block) {
  *              semantic error thrown will carry a `source_location` span
  *              pointing at the offending statement.
  *
+ *  @throws {JssmError} If the document declares no transitions (for example a
+ *                      states-first document of only `state` blocks) — a
+ *                      machine requires at least one transition; also for
+ *                      repeated property definitions, group errors, and other
+ *                      semantic problems noted throughout.
+ *
  */
 function compile(tree) {
     const results = {
@@ -22836,6 +22842,14 @@ function compile(tree) {
     // for the same (source_state, action) by depth-specificity before any
     // further processing (the runtime would otherwise reject the duplicates).
     const assembled_transitions = resolve_transition_conflicts(results['transition']);
+    // A machine with no transitions cannot be constructed (and previously
+    // crashed right here with a raw TypeError reading `[0].from`).  This is a
+    // natural mid-authoring document shape — state blocks first, wiring later —
+    // and the editor's lint shows this message verbatim, so name the actual
+    // problem instead of leaking an internal error.
+    if (assembled_transitions.length === 0) {
+        throw new JssmError(undefined, 'This machine has no transitions, only declarations; a machine requires at least one transition (like `a -> b;`)');
+    }
     const result_cfg = {
         start_states: results.start_states.length ? results.start_states : [assembled_transitions[0].from],
         end_states: results.end_states,
@@ -23578,7 +23592,7 @@ var constants = /*#__PURE__*/Object.freeze({
  *  Useful for runtime diagnostics and for embedding in serialized machine
  *  snapshots so that deserializers can detect version-skew.
  */
-const version = "5.157.1";
+const version = "5.157.3";
 
 // whargarbl lots of these return arrays could/should be sets
 const { state_name_chars, state_name_first_chars, action_label_chars } = constants;

package/dist/cdn/viz.js

@@ -22775,6 +22775,12 @@ function fold_graph_config(aliases, explicit_block) {
  *              semantic error thrown will carry a `source_location` span
  *              pointing at the offending statement.
  *
+ *  @throws {JssmError} If the document declares no transitions (for example a
+ *                      states-first document of only `state` blocks) — a
+ *                      machine requires at least one transition; also for
+ *                      repeated property definitions, group errors, and other
+ *                      semantic problems noted throughout.
+ *
  */
 function compile(tree) {
     const results = {
@@ -22861,6 +22867,14 @@ function compile(tree) {
     // for the same (source_state, action) by depth-specificity before any
     // further processing (the runtime would otherwise reject the duplicates).
     const assembled_transitions = resolve_transition_conflicts(results['transition']);
+    // A machine with no transitions cannot be constructed (and previously
+    // crashed right here with a raw TypeError reading `[0].from`).  This is a
+    // natural mid-authoring document shape — state blocks first, wiring later —
+    // and the editor's lint shows this message verbatim, so name the actual
+    // problem instead of leaking an internal error.
+    if (assembled_transitions.length === 0) {
+        throw new JssmError(undefined, 'This machine has no transitions, only declarations; a machine requires at least one transition (like `a -> b;`)');
+    }
     const result_cfg = {
         start_states: results.start_states.length ? results.start_states : [assembled_transitions[0].from],
         end_states: results.end_states,
@@ -23603,7 +23617,7 @@ var constants = /*#__PURE__*/Object.freeze({
  *  Useful for runtime diagnostics and for embedding in serialized machine
  *  snapshots so that deserializers can detect version-skew.
  */
-const version = "5.157.1";
+const version = "5.157.3";
 
 // whargarbl lots of these return arrays could/should be sets
 const { state_name_chars, state_name_first_chars, action_label_chars } = constants;

package/dist/cli/fsl-export-system-prompt.cjs

@@ -108,7 +108,7 @@ function parseFslArgs(argv, spec) {
   return { positional, flags, helpText };
 }
 
-const getVersion = () => "5.157.1";
+const getVersion = () => "5.157.3";
 const SPEC = {
   flags: {
     help: { short: "h", boolean: true },