(Global) rimraf: command not found about generator-jhipster-nodejs HOT 11 CLOSED

I've had those "rimraf" issues in the past, and I probably installed it globally to fix this, so I hope there isn't a bigger issue here

from generator-jhipster-nodejs.

Yes, don't hesitate!! I'm clearly not doing everything in the project, the best and only way to get that kind of thing moving is through tickets, so the right person can take it. And if it doesn't move fast enough I can give bug bounties :-)

from generator-jhipster-nodejs.

Hi @manekinekko , thanks for your feedback!
I have a question for you.. do you have performed the npm install under the server folder? I tell you that, because, as you can view on the server package.json sample app, there is rimraf dependency. I have tested this sample app and it works, according the command to build and start the app, so you can tell me all the commands that you have tried? Please refer to the general README and the server/README generated, where are explained all the tasks to run and build the app, so that you can give me more feedbacks and eventually a review for a better documentation.
If your problem is in the generator running, execute the commands indicated in the CONTRIBUTING.MD.
Thanks

from generator-jhipster-nodejs.

Hi @manekinekko, just a last advice... If you have still issues, run the blueprint with jhipster --blueprint nodejs --skip-install. Maybe it's a problem of a install hook. Thanks

from generator-jhipster-nodejs.

That's not something we recommend for many reasons. Usually, the recommendation is to depend as less as possible on global packages.

from generator-jhipster-nodejs.

@manekinekko for me it' s very strange, I have run the generator in various machines without rimraf installed globally and it works.
However I have checked, and rimraf is globally installed as a transitive dependency by yeoman.
Finally, I haven't undestood your seven command take /tmp/demo-app.
Maybe you aren't or you don't have created a new directory named "demo-app".
So, replace it with mkdir demo-app && cd demo-app, and rerun the generator.
I think that these are all the necessary commands, and if you have still problems, install globally rimraf, maybe you have some nodejs misconfiguration. Thanks for the feedback.

from generator-jhipster-nodejs.

@amanganiello90 FYI, take is a zsh command which creates and cd into a new folder.

I was also getting to open another issue where the installation process (of jhipster) is requesting me to install Java! But I'm gonna leave it here.

For context, as a Node and a JavaScript developer, I was called in by my colleague @jdubois to give my feedback on this project. My feeling so far is that If this blueprint is aimed to bring Node and JavaScript developers to jhipster, you probably need to review and improve the installation, the getting started and DX processes so these developers feel welcomed.

Cheers.

from generator-jhipster-nodejs.

Hi @manekinekko
I have already added in the backlog the issue #44 in order to leave java, according other feedbacks. The only problem is that I can modify the blueprint, but not the basic jhipster standard CLI that you must install before, so if it requires for the installation Java, the developer should have almost a JRE on his machine. Otherwise, we have to add an option or remove the constrant (and release a new version) in the basic generator-jhipster..it could be useful for all blueprints that not hava classes (as .Net blueprint)..Any suggestions @jdubois ?

from generator-jhipster-nodejs.

Indeed Java shouldn't be a requirement anymore for the jhipster CLI.
I haven't followed this, but I think this is handled on the JHipster CLI side, @amanganiello90 do you have some more information? Can you add a ticket on jhipster/generator-jhipster so this is tracked?

from generator-jhipster-nodejs.

Hi @jdubois,
There is a java check called from the general app index.js...Should I open a ticket and try to resolve it? Thanks

from generator-jhipster-nodejs.

OK wonderful!

from generator-jhipster-nodejs.