feat apilinks.json generator

[flakey5]

Closes #152

Opening this as a draft currently to get feedback on the approach since it's a bit non-trivial relative to the other generators. The apilinks.json file maps things exported by modules to their source locations on Github.

Example:

{
  "SomeClass.prototype.var": "github.com/nodejs/node/tree/<hash>/lib/file.js#L100"
}

This means we need to parse the module's javascript source in addition to its markdown.

What the current approach does is doing:

• Adds another loading & parsing step for the js source files
  • acorn is used for parsing the source files
  • This intakes .js files, so to run it you need to do pass in node/lib/*.js as the input
  • This is dependent on the Markdown source parsing since it uses the source_link metadata in the docs
• Exposes the parsed js ast to other generators by adding the ast-js generator
• api-links generator is based off of the ast-js result

[ovflowd]

@flakey5 do you need review here? I think I forgot to review this PR!

[flakey5]

do you need review here

As far as the approach yes please

[ovflowd]

Approach in general sounds good; Just, some of these utilities are way too complex and big and the git manipulation scripts are possibly dangerous or at least an easy vulnerability hell.

[ovflowd]

Also, @flakey5 this https://github.com/syntax-tree/estree-util-visit is what I was referring to use to walk through the Nodes of the source code. Since acorn generates an AST that is compatible with estree.

[ovflowd]

@flakey5 there are PR conflicts. Could you fix'em?

[ovflowd]

This is such a big function. I'd rather have a dedicated file for each one of these "cases" or dedicated functions on a separate file, just to reduce the chunk of this function. Pretty much just thinking on reusability.

Then you could have a map:

import identifierHandler ...

const typeHandlers = {
  'Identifier: identifierHandler,
  ...,
};

[ovflowd]

This applies for all these large function bodies here. You can create a sub directory. I think it becomes easier to read, easier to maintain. And if you have different functions for handling identifiers or expressions, etc. Simply make multiple exports for a file that handles everything related to a given type.

[ovflowd]

Note that this applies to all the helper functions you've made on all these different files. Let's decrease the size of these functions.

[ovflowd]

So far looking good. Left more comments, will review more once they are addressed-