Gloss Tools Home 繁體中文 Switching language or leaving the page discards the current draft.

Module Dependency Reduction

Find a cycle or group build modules by dependency stage. Inspect alternate paths that make a direct edge redundant. Data stays in the current page draft; nothing is uploaded or stored.

One module per line, up to 100. A name starts with a letter and contains only letters, digits, underscore, hyphen, or period, up to 32 characters; case matters.

One edge per line, written as “prerequisite>dependent”. Both ends must be registered modules, with no duplicate edges, up to 400 edges. Empty means no edges. A self-loop is valid input but is reported as a cycle.

Format details

Modules: at most 3,300 characters and 100 lines; edges: at most 26,400 characters and 400 lines. One trailing line break is ignored. Validation order: size and characters first, then empty content, row count, name format, and duplicates; edges are checked in order for shape, unknown endpoints, and duplicates. The first error names the field and line number.

The audit shows dependency stages (modules in one stage have no ordering dependency between them), an alternate path for each redundant edge, or the cycle that blocks ordering. The report downloads as a JSON file.

Nothing entered yet. Enter modules and edges, or load the example.

Frequently asked questions

Does an alternate path make a dependency safe to delete?

It proves reachability only. Review any extra meaning of the direct dependency.

Are partial stages shown for a cycle?

Fix the listed cycle and run the audit again.