Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Error on aofl init command on Windows #11

Closed
raybarrera opened this issue Dec 27, 2018 · 1 comment
Closed

Error on aofl init command on Windows #11

raybarrera opened this issue Dec 27, 2018 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@raybarrera
Copy link

Describe the bug
When attempting to init a new project using the aofl cli tools, I get an error in events.js

To Reproduce
Steps to reproduce the behavior:

  1. Install aofl/cli using the npm command (npm i -g @aofl/cli)
  2. [npx] aofl init path/to/myproject
  3. observe the following error:
running... npm i

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
    at onErrorNT (internal/child_process.js:407:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
    at onErrorNT (internal/child_process.js:407:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Desktop (please complete the following information):

  • OS: Windows 10, Command Prompt or Cmder
  • npm version: 6.5.0
  • node version: v10.14.2
@arianics arianics self-assigned this Dec 27, 2018
@arianics arianics added the bug Something isn't working label Dec 28, 2018
@arianics
Copy link
Contributor

arianics commented Dec 28, 2018

fixed in v1.4.0 5f30e1b

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants