-
Notifications
You must be signed in to change notification settings - Fork 16
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
Unable to run Kevoree Hello World #86
Comments
To get a verbose output, you can add |
Did you install the latest Yeoman generator ? npm i -g generator-kevoree@latest If your "test" directory is an old project, you might want to update the generator, re-generate a more up-to-date project, and then run it. |
I created an empty folder, test2. Here is what I did:
|
Do you have |
I have installed the latest Yeoman before I tried this. Running with kevoreejs does not work either.
|
It looks like Kevoree cannot spawn a child process because it cannot find the |
Yes, npm is in PATH |
Can you push your example, so I can have a look at it ? |
Sure, I could, but I have not done anything but create a new project using Yeoman in an empty folder. Knut Eilif got the same issue following the same steps. |
Note that I have a similar problem with the smart NPM stuff under Windows. It works with Linux, though. |
Pushed it under training/2.Kevoree_Basics/6.Contrib/Tellu/YeomanTest |
Ok, so I've made some investigation, and it looks like a Node.js bug on the Windows platform. |
I'm gonna rollback the npm resolver to a previous version in order for Windows users to be able to run Kevoree Js. But this trick was used to prevent npm to take too much memory. With the rollback, and so the old version, npm will still live in the same process, and so take at least 50mb of RAM if not more |
Use
Then: rm -rf node_modules
npm i |
You should get |
I think I did it correctly, but now I get:
|
Check in your |
The version is 5.6.2 |
Yeah, my bad, you should use 5.6.1, not 5.6.2 |
Alright, got a bit further
|
Do you have the |
By the way, I've found a workaround, in order to run npm in a child_process as intended in Windows too. I'm gonna release that ASAP so that you do not have to use an old version of grunt-kevoree. |
Yes, it is in the root directory. Ok, great. |
It works under Windows for me. Did you remove the |
Didn't remove it at first, but tried deleting it now. Same issue as before. |
Lunch, will be back in an hour. |
Alright. Should be fixed. Go get the latest everything :) Lunch time too. Tell me if anything fails. |
If you are interested, this does the trick. |
I deleted Do I need to do anything else to get all the latest stuff? I now get this:
|
|
I'm investigating |
Damn. There were a bunch of problems with my latest releases. Sorry for that. I've stabilize them in the latest I'll try to find a workaround for that too. But for now, you can use kevoree-js if you start your terminal as Root in Windows (right click > Run as Administrator) |
Ok, got Hello World to work, thanks. |
On Windows, using Git Bash.
Failed to run grunt kevoree after generating a hello world project using Yeoman. This is copy/paste of the command line:
The text was updated successfully, but these errors were encountered: