Cannot enlarge memory arrays. about ngd HOT 13 OPEN

@manekinekko is this experimental approach somehow available (branch or something)?

from ngd.

this issue comes from the Viz dependency. We're trying another approach. Will keep you updated.

from ngd.

@DaSchTour the trick from @manekinekko is for compodoc installed globally in your system.

npm i -g @compodoc/compodoc

from ngd.

any update on this?

from ngd.

so this tool is useless?

from ngd.

same here

from ngd.

@vogloblinsky is working on a possible solution to fix this.
To give you more context, this "solution" will allow rendering the graph deps on the client side (the user's browser). In fact, the library we depend on viz.js doesn't deal well with large projects. It simply crashes. In addition, it's not maintained anymore.

In the meantime, we've included a "workaround" that simply skip the graph that are very large and don't render. You still should have the rest of the documentation generated and working properly (but without the affected graphs).

To do so, just run compodoc via a node script:

package.json

{
   "scripts": {
      "reports:doc": "node ./tools/scripts/compodoc.js"
   }
}

tools/scripts/compodoc.js

const { spawn } = require('child_process');
const cmd = spawn('compodoc', ['-p', 'src/tsconfig.app.json', '-d', 'reports/documentation/']);
cmd.stdout.pipe(process.stdout);
cmd.stderr.pipe(process.stdout);

Doing so will trick your CI and not mark your build as FAILED.

from ngd.

@manekinekko I tried your solution but it doesn't work. It just throws an error

events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: spawn compodoc ENOENT
    at _errnoException (util.js:1022:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
    at onErrorNT (internal/child_process.js:372:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:695:11)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3

I also have no idea how this should work because compodoc is not registered as a binary anywere.

from ngd.

we're experimenting an other approach which would be rendering the graph on the client side (taking into account some performances issues).

from ngd.

Have the same issue here? This thread is 10 months old. Any news?

from ngd.

Same issue. Any news?

from ngd.

running compodoc via a node script worked for me.

from ngd.

Same thing on windows, can't generate main diagram.

from ngd.