Closed buddhasaikia closed 5 years ago
Do you have a public repository or a project that you can send me so I can try to reproduce this issue?
Aah! Sorry bro, that was not a public repo. I will test it on a public repo & let you know. Thanks
Now I am receiving this error while running daggraph
from current project directory-
command-
Analyzing dagger components and modules..
TypeError: pending.then is not a function
at FileHound._searchAsync (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\filehound\lib\filehound.js:705:22)
at tryCatcher (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\util.js:16:23)
at MappingPromiseArray._promiseFulfilled (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:61:38)
at MappingPromiseArray.PromiseArray._iterate (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:114:31)
at MappingPromiseArray.init (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\promise_array.js:78:10)
at MappingPromiseArray._asyncInit (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\map.js:30:10)
at Async._drainQueue (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:138:12)
at Async._drainQueues (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\user\AppData\Roaming\npm\node_modules\daggraph\node_modules\bluebird\js\release\async.js:17:14)
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
Same issue here, on Windows 10 browser has same issue
Uncaught SyntaxError: Unexpected token K in JSON at position 55
at JSON.parse (<anonymous>)
at dependency_tree_graph.html:75
Unfortunately I can't grant you access to repository. What is funny actually on Linux Mint site gets generated perfectly and works like a charm.
@dvdciri Hello, I have the same problem with parsing. You can reproduce this issue with my project:
Can you please double check if you still have the issue with the new release 0.3.3? Thanks
@dvdciri Still reproduces with the same error. Thanks
I am able to show the graph by not using JSON.parse() and assigning it directly to the variable.
From:
const flare = JSON.parse("{"children": []}")
To:
const flare = {"children": []}
Create, maybe we can do this change, if you fancy open a PR feel free! Thanks
Description
Found the following error on inspect (Chrome browser)
dependency_tree_graph.html
Steps to reproduce
Expected behaviour
Screenshot