Type annotations

[toasted-nutbread]

This change adds JSDoc type annotations to everything and fixes any relevant code/bugs that arose due to incorrect type handling.

This is a massive change and I have not verified that everything 100% works as it should, but some cursory testing appears okay.

[github-actions]

✔️ No visual differences introduced by this PR.

View Playwright Report (note: open the "playwright-report" artifact)

[djahandarie]

Insanely impressive. Thank you so much. Once the CI failure is fixed, assuming the tests pass I think we can just merge it 👀

[djahandarie]

Thank you!!

[djahandarie]

@toasted-nutbread I noticed that this PR doesn't add the test-ts check to CI.

I was going to put it into CI myself, but then I noticed that tsc is actually failing for me locally:

[nix-shell:~/yomitan]$ npx tsc --noEmit --project jsconfig.json
/home/darius/yomitan/node_modules/typescript/lib/tsc.js:116479
      throw e;
      ^

RangeError: Maximum call stack size exceeded
    at getTypeAtFlowNode (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65168:31)
    at getTypeAtFlowCondition (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65359:24)
    at getTypeAtFlowNode (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65203:18)
    at getTypeAtFlowBranchLabel (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65417:26)
    at getTypeAtFlowNode (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65211:48)
    at getTypeAtFlowCondition (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65359:24)
    at getTypeAtFlowNode (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65203:18)
    at getTypeAtFlowCondition (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65359:24)
    at getTypeAtFlowNode (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65203:18)
    at getTypeAtFlowBranchLabel (/home/darius/yomitan/node_modules/typescript/lib/tsc.js:65417:26)

Node.js v18.17.1

Does this happen in your environment?

[toasted-nutbread]

Oh good point, I didn't realize that the CI wasn't just running npm test.

Regenerate your files in ext/lib, I made a change which adds a // @ts-nocheck header to them. I think that's where that issue was stemming from.