-
Notifications
You must be signed in to change notification settings - Fork 70
Support jsdoc
and typedoc
doctools
#147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Versions on images from production today:
I can support this guess by parsing the
Reference: https://www.npmjs.com/package/typedoc |
Building 7.x using #174 generates this warning message
I'm not sure if it's important or not and I think it was already present in this image. Maybe |
I'm thinking about how to handle this case in the new images (#166). I prefer if we don't include these at this moment because we will need to handle versioning again on the base image. I'm not aware how many users are currently using these packages and if there is a good way to install them (without hacking the On the other hand, these are documentation tools (like Sphinx or MkDocs). Because of that, if we want to support them, we should allow them to be installed as any other doctool. I'd like to add support for them on the "Future builders" when we allow custom commands. |
It seems this is not required anymore. New Docker images does not include |
We need to pin these dependencies to make the image reproducible over time:
https://github.com/rtfd/readthedocs-docker-images/blob/89bb0b60820ab0960d5cc875667ba2570c5ffb99/Dockerfile#L128-L130
The text was updated successfully, but these errors were encountered: