[BUG] : Error during graph generation about compodoc HOT 23 CLOSED

Ok fine.
I will test your configuration later. I am downloading a modern.ie Windows 10 virtual machine for testing.
The tests are just running with npm, but while Travis now supports Yarn, i will add a test case with it too.

from compodoc.

What is your environment ?
OS ? node/npm version ?

from compodoc.

@emolr
What is your environment ?
OS ? node/npm version ?

from compodoc.

I have the same issue. Running Windows 10 (1607), NodeJs v6.4.0 and NPM 3.10.3. I installed compodoc by listing it as a dev dependency and using yarn (v0.15.1) to fetch it.

[10:04:43] Copy main resources
[10:04:43] Process main graph
[10:04:43] Error during graph generation: : 'C:\Dev\Repos\my-project\src\Just.A.Namespace\node_modules\.bin\ngd' is not recognized as an internal or external command,
operable program or batch file.

from compodoc.

@johanbenschop can i have a screenshot of your node_modules.bin folder ?

from compodoc.

I'll do a pastebin instead: http://pastebin.com/C4hiL2TZ.

from compodoc.

And your package.json please ?

It seems that ngd is not installed during compodoc installation.

from compodoc.

The package.json: http://pastebin.com/Gjaswu56. I'm going to try from an empty node_moduels directory with npm.

from compodoc.

Thanks, did you confirm this scenario for the test case ?
install node 6.4.0
install yarn 0.15.1
use package.json file in an empty folder
and run yarn

from compodoc.

Now it works with a node_modules with NPM. Removed the yarn.lock and tried it with that, no ngd again, so this seems to be a yarn issue. Thanks for your time!

from compodoc.

The related GitHub issue from the yarn project about this: yarnpkg/yarn#760. It looks like they fixed it and later reverted the fix for some reason.

from compodoc.

@johanbenschop Yarn 0.18.0 just released (https://github.com/yarnpkg/yarn/releases/tag/v0.18.0), bug #760 seems closed, could you test on your side ?
Thanks

from compodoc.

After testing 0.18.0 and last nightly-build, the bug is still present in yarn...
yarnpkg/yarn#760 (comment)

from compodoc.

I'm getting the same issue here, not using Yarn.

Mac OS 10.11.3 (El Capitan)
NPM version 3.10.9
Node version 7.2.1

Let me know if I can help in some way!

from compodoc.

@IckleChris : for what kind of project ? an angular-cli one ?
I cannot reproduce your bug with your environment. Using Node.js 7.2.1, and this demo project, the npm run doc doesn't failed.

from compodoc.

Yes angular-cli. When I get the chance today I'll try with a fresh project.

from compodoc.

Same issue is of course present with a fresh project. The path in the error (/usr/local/lib/node_modules/.bin/ngd) doesn't exist on my machine beyond node_modules - node binaries are stored in /usr/local/bin. Either way, ngd doesn't exist on my machine.

from compodoc.

ok can i have your angular-cli version ?
compodoc installed in global ?

from compodoc.

I've just tried installing compodoc locally within the project and that works fine. Issue only appears to happen when installed globally. That seems to be the case regardless of whether the script added to package.json is

"compodoc": "./node_modules/.bin/compodoc -p src/tsconfig.json"

or

"compodoc": "compodoc -p src/tsconfig.json"

angular-cli version is 1.0.0-beta.22-1

from compodoc.

@IckleChris
Cannot reproduce your bug.
On a fresh Mac OSX El Capitan :

• installed Node.js 7.2.1

• installed npm 3.10.9

• installed compodoc in global : npm i -g compodoc

• cloned demo repo : https://github.com/compodoc/compodoc-demo-todomvc-angular2

• launch compodoc -p src/tsconfig.json -s and it works fine

• which compodoc gives me : /usr/local/bin/compodoc

• compodoc is located here : /usr/local/lib/node_modules/compodoc

• ng is located here : /usr/local/lib/node_modules/compodoc/node_modules/angular2-dependencies-graph

from compodoc.

this may be related to... does any of your code contain double forward slashes for commented code?

from compodoc.

Closing, last version use ngd directly without CLI call as before. Give it a try ;)

from compodoc.

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

from compodoc.