Failed to parse relative imports for ${scriptPath}: ${e}. De

Error message

Failed to parse relative imports for ${scriptPath}: ${e}. Dependency tracking for relative imports will be disabled.

What it means

Guard catch in extractRelativeImports: the language parser (wasm TS/Python import parser) threw while scanning the script's code for relative imports. Dependency tracking for relative imports of this script is disabled — its imports won't be tracked in sync/staleness, but the push continues.

Source

Thrown at cli/src/utils/relative_imports.ts:36

  language: ScriptLanguage
): Promise<string[]> {
  try {
    switch (language) {
      case "bun":
      case "nativets":
      case "deno": {
        const { parse_ts_relative_imports } = await loadParser("windmill-parser-wasm-ts");
        return parse_ts_relative_imports(code, scriptPath);
      }
      case "python3": {
        const { parse_py_relative_imports } = await loadParser("windmill-parser-wasm-py-imports");
        return parse_py_relative_imports(code, scriptPath);
      }
      default:
        return [];
    }
  } catch (e) {
    log.warn(`Failed to parse relative imports for ${scriptPath}: ${e}. Dependency tracking for relative imports will be disabled.`);
    return [];
  }
}

View on GitHub (pinned to e474e8803c)

Solutions

Fix the syntax error in the script that breaks the parser
Update the CLI so parser/wasm versions handle the construct
Manually track the dependency or import it by path so sync still sees it

Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at cli/src/utils/relative_imports.ts:36 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.

AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03). Data as JSON: /api/errors/b311ce70a08a28d4. Report an issue: GitHub.