Windows 11 failed installation

[sergeliatko]

Hi guys, I tried to install the work OS latest on Windows via the recommended mpx command, and here is what I've got.

============================================================
WorkOS AuthKit Installer Run: 2026-05-20T06:02:32.159Z

[2026-05-20T06:02:32.160Z] ℹ️ INFO: Wizard starting with options: {
"debug": false,
"dashboard": false,
"local": false,
"ci": false,
"skipAuth": false,
"installDir": "C:\Users\serge\PhpstormProjects\creddoors"
}
[2026-05-20T06:05:18.567Z] ❌ ERROR: Wizard failed with error: Error: Could not detect framework integration
at error (file:///C:/Users/serge/AppData/Local/npm-cache/_npx/9662a4027af8808f/node_modules/workos/dist/lib/installer-core.js:547:47)
at assign.resolveAssign [as resolve] (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\assign-9f37914d.cjs.js:74:67)
at resolveAndExecuteActionsWithContext (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:2408:56)
at resolveActionsAndContext (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:2431:21)
at microstep (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:2161:17)
at Object.macrostep (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:2513:18)
at StateMachine.transition (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\StateMachine-4c92941f.cjs.js:397:37)
at Actor._process (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:925:30)
at Mailbox.flush (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:45:12)
at Mailbox.enqueue (C:\Users\serge\AppData\Local\npm-cache_npx\9662a4027af8808f\node_modules\xstate\dist\raise-eb8e9de6.cjs.js:37:12)
[2026-05-20T06:05:18.599Z] ⚠️ WARN: [credential-store] keyring: entry exists but data is null/empty

What would be my next steps, please?

[sergeliatko]

This is what my agent says:

Root cause: This looks like a WorkOS CLI Windows bug in workos@0.15.1, not a project problem.

The CLI’s registry loader imports integration files using a raw Windows path, such as:

C:\Users...

Node ESM rejects that path unless it is converted to a file:// URL. That explains the earlier repeated error:

ERR_UNSUPPORTED_ESM_URL_SCHEME ... Received protocol 'c:'

Once those integration modules fail to load, the registry is effectively empty. The next symptom is therefore:

Could not detect framework integration

Your repo should be detectable as React. package.json has react, no next, no react-router, and no @tanstack/react-start.

Potential solutions:

1. Best practical workaround: run the installer from WSL2/Linux, inside a Linux-path checkout of the repo. That avoids C:... ESM imports entirely.

2. Report the issue upstream with the log and this likely fix:

In workos/dist/lib/registry.js, WorkOS should import integration modules via pathToFileURL(indexPath).href, not import(indexPath).

Conceptual patch:

import { fileURLToPath, pathToFileURL } from 'node:url';

const mod = await import(pathToFileURL(indexPath).href);

3. --integration react is documented by WorkOS for detection failures, but in this specific Windows loader failure it probably will not help because the registry still cannot load the React integration module.

Sources: WorkOS CLI docs confirm npx workos@latest install, --integration , and issue reporting at GitHub:

https://workos.com/docs/authkit/cli-installer

The package metadata points to:

https://github.com/workos/cli

[sergeliatko]

WorkOS CLI Windows ESM Integration Loader Failure

Summary

workos@0.15.1 fails to load installer integrations on native Windows because dist/lib/registry.js dynamically imports raw absolute Windows paths such as C:\Users\...\node_modules\workos\dist\integrations\react\index.js. Node's default ESM loader rejects that path form because it treats c: as an unsupported URL scheme.

Environment

• OS: Windows
• Shell: PowerShell
• Node: v24.12.0
• npm: 11.12.1
• WorkOS CLI package: workos@0.15.1
• Command: npx workos@latest install

Error

The installer printed this error for each integration directory:

Failed to load integration from react/: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

After all integrations failed to load, the installer could not detect the framework:

Could not detect framework integration

Root Cause

registry.js builds an absolute filesystem path with join(integrationsDir, dir, 'index.js') and passes that string directly to dynamic import(...). On Windows, that produces a C:\... path. Node ESM requires Windows absolute paths to be converted to file:// URLs before importing.

Tested Fix

The local test patched the registry loader to import pathToFileURL(indexPath).href. After that change, the registry loaded all integrations successfully and the project detected as react.

The attached patch shows the intended source change and the compiled JavaScript equivalent that was tested locally.

Additional Local Note

On this machine, WorkOS CLI authentication also required NODE_OPTIONS=--use-system-ca because Node fetch failed certificate verification while Windows trusted the endpoint. This appears separate from the ESM loader issue.

Patch attached (not reviewed)

workos-cli-windows-esm-loader.patch

[nicknisi]

Thanks for the report. I opened #156 to address and am testing on Windows.