Types of errors:

• NeedPackageSources: Raised by Elm.TypeInference.init when extra dependency sources are needed to analyze whether a docs.json-mentioned internal type is a record or a custom type. Provide these files in sourcesToResolveAmbiguity in the next Elm.TypeInference.init call.

• MissingModuleName: Raised when a File has an empty module name.

• DuplicateModule: Raised by Elm.TypeInference.init when two of the projectFiles declare the same module.

• ImpossibleDocsType: for hand-crafted docs.json with nonsensical data, like a 4-tuple. Real docs.json files emitted by the Elm compiler should never produce these.

• ImpossibleType: Similar but for hand-crafted elm-syntax Files given in sourcesToResolveAmbiguity.

• AmbiguousModuleOwner: Raised when a type in a dependency's docs.json or sources refers to a module (moduleName) exposed by more than one package visible to that dependency.

• TypeNotFound, WrongTypeArity, RecursiveAlias: Raised when a type alias in sourcesToResolveAmbiguity mentions a type that can't be found (eg. because the docs.json of the package defining it wasn't provided), applies a type to the wrong number of arguments, or refers to itself. The Elm compiler rejects all of these when publishing a package, so they only happen with hand-written sourcesToResolveAmbiguity or docs.json files, or with incomplete dependency information.

Where in a dependency an error was found.

Render an error for diagnostic output.