Skip to content

Conversation

@voxelstack
Copy link

@voxelstack voxelstack commented Dec 28, 2025

Closes #285

I considered updating search_node_modules to return a command that may or may not include "node" but since including it fixes the Windows issue without breaking other platforms I went with this smaller change instead. This is also consistent with the jsdocinvocation where "node" is always part of the command.

On my windows machine the version call succeeds now but the project I'm testing it on is throwing an unrelated error about ESM URL schemes. Because of that I still haven't gotten a successful run after my changes, working on it now.

nox is also causing errors when I run it locally so after I get a successful run I'll try and check the tests locally with WSL.

@voxelstack
Copy link
Author

voxelstack commented Dec 28, 2025

I guess there are more issues with Windows apart from running typedoc. What I'm seeing now is:

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:'

I suspect that must be caused by importHooks.mjs but the fallbackUrl starts with file: and TYPEDOC_NODE_MODULES is being set to the correct path. Having a little trouble with this one.
It's caused by paths being given to --import, so that is easily solvable by adding "file:///" + to the imports when running on Windows.

Now what I'm investigating is why the resolver is getting two absolute paths joined together: 'file:///D:/dev/ceres/docs/file:/C:/Users/voxel/pipx/venvs/sphinx-autobuild/Lib/site-packages/sphinx_js/js/main.ts'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows build fails with "WinError 193" when js_language = 'typescript'

1 participant