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

2.0.2 version in Windows causing errors #30

Closed
Tom910 opened this issue Jul 20, 2016 · 4 comments · Fixed by #32 or #34
Closed

2.0.2 version in Windows causing errors #30

Tom910 opened this issue Jul 20, 2016 · 4 comments · Fixed by #32 or #34

Comments

@Tom910
Copy link
Contributor

Tom910 commented Jul 20, 2016

I updated to version 2 and is now on all Windows computers error. In this case all is well on the mac.

{
  "scripts": {
     "lint-staged": "lint-staged",
     "eslint:fix": "eslint --fix",
     "stylelint:less": "stylelint --syntax=less",
     "git:add": "git add"
  },
  "lint-staged": {
      "*.@(js|jsx)": [
        "eslint:fix",
        "git:add"
      ],
      "*.less": [
        "stylelint:less"
      ]
  },
  "pre-commit": [
      "lint-staged"
  ],
}
25h25hevents.js:154
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:475:9)
    at process._tickCallback (node.js:389:17)
pre-commit:
pre-commit: We've failed to pass the specified git pre-commit hooks as the `lint-staged`
pre-commit: hook returned an exit code (1). If you're feeling adventurous you can
pre-commit: skip the git pre-commit hooks by adding the following flags to your commit:
pre-commit:
pre-commit:   git commit -n (or --no-verify)
pre-commit:
pre-commit: This is ill-advised since the commit is broken.
pre-commit:

npm 3.6.0/3.9.3, node 5.6.0/6.2.1

@okonet
Copy link
Collaborator

okonet commented Jul 22, 2016

Hey! Sorry I don't have windows to test it. I'm happy to accept a PR that fixes it though.

@Tom910
Copy link
Contributor Author

Tom910 commented Jul 22, 2016

Ok, on the weekend I try to understand what the problem is

@okonet okonet mentioned this issue Jul 22, 2016
Merged
7 tasks
@okonet
Copy link
Collaborator

okonet commented Jul 22, 2016

@Tom910 can you try this branch out and let me know if it fixes the issue?

#32

Thanks!

@Tom910
Copy link
Contributor Author

Tom910 commented Jul 23, 2016

@okonet Yes, to issue #32, this error has been corrected

Thank you!

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

Successfully merging a pull request may close this issue.

2 participants