Skip to content
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

Invalid command: karma completion #2351

Closed
nopnop opened this issue Sep 9, 2016 · 1 comment · Fixed by karronoli/redpen#10 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed

Invalid command: karma completion #2351

nopnop opened this issue Sep 9, 2016 · 1 comment · Fixed by karronoli/redpen#10 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132

Comments

@nopnop
Copy link

nopnop commented Sep 9, 2016

Expected behaviour

karma completion should return the bash completion script as described by karma --help and `karam completion --help

  • OR -

karma --help should not list the karma completion command anymore

Actual behaviour

karma completion
{ Error: ENOENT: no such file or directory, open '(...absolute path to...)/karma/scripts/karma-completion.sh'
    at Error (native)
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '(...absolute path to...)/karma/scripts/karma-completion.sh' }

Environment Details

  • Karma version (output of karma --version): 1.2.0
  • Relevant part of your karma.config.js file: not relevant

Steps to reproduce the behaviour

  1. Install karma with npm (not git clone)
  2. Run karma --help (see the listed karam completion command)
  3. Run karma completion

Reason

The .npmignore file ignore scriptsdirectory

@dignifiedquire
Copy link
Member

Thank you for the report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants