-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"npm install" doesn't work for ember-cli-jsdoc #19
Comments
I think step 1 should be |
@SpikedKira That way does not invoke the Ember CLI ecosystem, which you need for the installation of this addon, as it will then leverage the blueprint, so @ewoody When you say that jsdoc is not installed correctly what are you seeing? Can you provide more details? I just started seeing something weird the other day in a CircleCI environment and am curious of the characteristics you are seeing. |
node_modules\ember-cli-jsdoc\node_modules.bin folder doesn't have jsdoc and jsdoc.cmd at all. |
There is no problem of installation on my local PC, the problem is our CI server can't use "ember install" as a step to build project. |
CAUSE
FIX
|
@ewoody unrelated to what is the root cause of this issue, I'm curious about your comment in #19 (comment) regarding your CI server not being able to use |
https://github.com/softlayer/ember-cli-jsdoc/releases/tag/v1.3.2 has been released to address this issue. |
binary files have not been copied in right location by npm install. that is - the files in PROJECT_FOLDER\node_modules\ember-cli-jsdoc\node_modules.bin should be copied to PROJECT_FOLDER\node_modules.bin so that our CI server doesn't work still. |
@ewoody Which version of Node are you using on your CI server? Have you re-ran the build with no cache to ensure you are getting the latest version of this addon? |
I have verified that the v1.3.2 works for me after I deleted entire PROJECT_FOLDER\node_modules and re-run npm install. Thank you for this fix. |
This issue still exists with v1.4.0. Steps to reproduce:
I can confirm that #19 (comment) does resolve the issue. |
I have been able to recreate the scenario outlined in #19 (comment) including how to resolve it. If when following the same steps instead of running Step 3:
then the problem no longer occurs. @mrryanjohnston I am going to reopen this issue and spend some time researching a few more items, which may possibly result in opening an issue with Ember CLI (depending on what some of my current thoughts to research turn up). I will update this issue with appropriate links and information as they occur. Thank you for reporting this behavior. |
Have found this that is sort of related behavior - http://stackoverflow.duapp.com/questions/37142438/npm-node-modules-bin-symlinks |
Believe this is resolved by https://github.com/softlayer/ember-cli-jsdoc/releases/tag/v1.4.1 |
Reproduce path -
Expected
Since after step 1, "ember-cli-jsdoc": "1.3.1", is added in package.json, I expected the "npm install" should install ember-cli-jsdoc addon in a clean directory. It is normal for other ember addons, and it is useful for continuous integration build server.
Problem
after npm install on step 3, jsdoc is not installed correctly.
The text was updated successfully, but these errors were encountered: