-
Notifications
You must be signed in to change notification settings - Fork 33
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
Breaking change in minor version #83
Comments
This was referenced May 7, 2016
ljharb
added a commit
to ljharb/eslint-config
that referenced
this issue
May 7, 2016
- Lock `eslint-find-rules` to 1.8.x due to sarbbottam/eslint-find-rules#83
ping @sarbbottam @kentcdodds |
ljharb
added a commit
to ljharb/javascript
that referenced
this issue
May 7, 2016
Locking `eslint-find-rules` to `v1.8` due to sarbbottam/eslint-find-rules#83
@ljharb extremely sorry about it. We use |
sarbbottam
added a commit
that referenced
this issue
May 7, 2016
id-global check should not have been part of minor release fixed #83
sarbbottam
added a commit
that referenced
this issue
May 7, 2016
is-global check should not have been part of minor release fixed #83
sarbbottam
added a commit
that referenced
this issue
May 7, 2016
is-global check should not have been part of minor release fixed #83
Thanks! |
ljharb
added a commit
to ljharb/eslint-config
that referenced
this issue
May 8, 2016
Per issue fixed in sarbbottam/eslint-find-rules#83
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So, first, 93a68b6 is a breaking change, and should not have been released as a minor version.
Second, it is failing for me when run as a local utility. Using
npm run-script
s,eslint-find-rules
can be invoked directly, sincenpm
puts it in the PATH - so your method of determining "is global" is flawed.The text was updated successfully, but these errors were encountered: