windmill-labs/windmill · error

No mocked API file path provided at env variable WM_MOCKED_A

Error message

No mocked API file path provided at env variable WM_MOCKED_API_FILE. Using empty mocked API.

What it means

Informational warning in the TS client's mock loading: WM_MOCKED_API_FILE is not set (and no usable mock was loaded), so an empty mocked API (no variables, no resources) is used. Harmless outside mocked/test runs.

Source

Thrown at typescript-client/client.ts:1534

    const fs = await import("node:fs/promises");
    const file = await fs.readFile(mockedPath, "utf-8");
    try {
      mockedApi = JSON.parse(file) as MockedApi;
      if (!mockedApi.variables) {
        mockedApi.variables = {};
      }
      if (!mockedApi.resources) {
        mockedApi.resources = {};
      }
      return mockedApi;
    } catch {
      console.warn("Error parsing mocked API file at path", mockedPath);
    }
  } catch {
    console.warn("Error reading mocked API file at path", mockedPath);
  }
  if (!mockedApi) {
    console.warn(
      "No mocked API file path provided at env variable WM_MOCKED_API_FILE. Using empty mocked API."
    );
    mockedApi = {
      variables: {},
      resources: {},
    };
    return mockedApi;
  }
}

interface MockedApi {
  variables: Record<string, string>;
  resources: Record<string, any>;
}

function parseResourceSyntax(s: string | undefined) {
  if (s?.startsWith("$res:")) return s.substring(5);
  if (s?.startsWith("res://")) return s.substring(6);

View on GitHub (pinned to e474e8803c)

Solutions

1. Set WM_MOCKED_API_FILE to the mock file path when mocking is intended
2. No action when running against a real workspace

When it happens

Trigger: Thrown at typescript-client/client.ts:1534 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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