Compilation problems

The preview stopped changing

A visible preview may be the last successful compile. Open the diagnostics or Document health panel and address the first relevant error. Go to source in the preview error banner, error list, or Health panel opens the relevant project file and selects the offending text. On mobile it returns to Editor; in desktop preview-only mode it restores both panels. Line and column numbers match the editor, including errors after rendered diagram blocks.

Package errors and errors without a source location do not offer a source jump. Context notes show where an include or function call led to the error; they are not additional warnings.

Check for unmatched brackets, missing quotes, or an unfinished function call. After fixing it, wait for automatic compilation or press Mod+Enter.

A file cannot be found

Check the exact path and capitalization. Image, include, and bibliography paths must refer to files present in the project. Paths are relative to the file that contains the reference.

If you renamed a file, update its references too.

For example, File not found: “references.bib” means you need to upload or create that bibliography file in Files, or correct the filename in #bibliography("references.bib"). The error points to the reference in your source, because the missing file itself cannot be opened.

Some browser compiler file-loading failures arrive as access denied even when the cause is a missing file. Tylor names the missing file when it can verify a literal reference against the project. Computed paths, escaped strings, and package-internal failures can still show the original compiler message; check the path and package contents before changing permissions.

A package cannot be found

For @local imports, verify the name and version in Local packages. Shared documents use the owner’s referenced packages; adding a same-named package to your own library does not replace them.

For @preview imports, check the version and your network connection. A package not already cached may require a download.

A font will not load

Open Fonts and verify the required family and faces are available. Reconnect if a download failed, then retry. Check fonts before replacing a typeface, since different metrics can change pagination.

The exported document looks wrong

Resolve diagnostics, wait for fonts, and review pending suggestions. Re-export and inspect the actual download. For a persistent problem, reduce it to a small example without private content and include the exact error and relevant source when requesting help.