Unable to run the docs

[bhavelyn]

Describe the bug
When I try to run npm run docs I get the following error:

Error: Tried to set an option (mode) that was not declared.
npm ERR! code 1
npm ERR! path /home/xxx/work/kubernetes-js-client
npm ERR! command failed
npm ERR! command sh -c typedoc src/gen/api

npm ERR! A complete log of this run can be found in:

** Client Version **
e.g. 0.12.0

** Server Version **
e.g. 1.19.1

To Reproduce
Steps to reproduce the behavior:

1. Clone the repo
2. npm install
3. npm run generate
4. npm run docs

Expected behavior
Docs to be generated

** Example Code**
N/A

Environment (please complete the following information):

• OS: Ubuntu
• NodeJS Version: 15.2.1 (also tried with v12.16.1 and v10.22.0)
• Cloud runtime: NA

Additional context
Add any other context about the problem here.

[bhavelyn]

Is there Documentation some place else or hosted ?

[bhavelyn]

Locally going back to typedocs@0.19.2 fixed it for me.

looks like this broke it - 2b8f1ab#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R99

Or may be my node version OR TS version is not compatible.

[brendandburns]

fwiw, the docs are generated and not super useful.

There are a bunch of examples here:
https://github.com/kubernetes-client/javascript/tree/master/examples

And the general Kubernetes API docs here:
https://kubernetes.io/docs/reference/

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.