Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

POC for documentation using typedoc and sphinx-js #37

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hemant-hc
Copy link
Member

@hemant-hc hemant-hc commented Aug 25, 2023

This POC uses typedoc and sphinx-js to generate documentation.

We need to specify the version of sphinx related packages in the constraints file because when the versions are not specified sphinx-js 1.0 is auto-installed, which is far older than the latest version 3.2.1, and lacks many of the features.

Sphinx-js supports a super old typedoc version 0.15.0 officially at least and I encountered another typedoc problem related to type errors reported in node_modules (which doesn't work even with --skipLibCheck for some reason) as well in my POC.

I think we can get it to work but it will require significant amount of time to debug and fix. Even then we might face issues with using latest typescript and typedoc. Perhaps it's better to just use latest typedoc with something like docusaurous?"

@hemant-hc
Copy link
Member Author

@sneridagh @stevepiercy I encountered some issues while making this POC, I have mentioned them in detail in the PR description.

@sneridagh
Copy link
Member

Maybe there's a more up to date plugin for sphinx...

@stevepiercy
Copy link
Collaborator

There's also a dependency conflict over Sphinx, even when I try to install sphinx-js from a fork by the Pyodide team.

$ bin/pip install git+https://github.com/pyodide/sphinx-js.git@master

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
myst-parser 2.0.0 requires sphinx<8,>=6, but you have sphinx 5.3.0 which is incompatible.
Successfully installed Sphinx-5.3.0 markupsafe-2.0.1 parsimonious-0.10.0 pydantic-1.10.12 regex-2023.8.8 sphinx-js-3.2.1

There are a few open issues and PRs on the sphinx-js project that indicate there is interest in its further development. There's been a fork, too.

It was worth a shot. Thank you for trying @hemant-hc.

It's OK to close this PR, or leave it open to get more exposure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants