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

Resolve vulnerabilities from npm audit #31

Closed

Conversation

toddmilliken
Copy link

Thanks for all the work on this awesome package!

After trying to resolve vulnerabilities in my local project using grunt-phplint, I believe that this package needs to be updated. I may not have done this correctly, so I'd appreciate some guidance as I understand there could be significant breaking changes.

I ran npm audit fix and followed prompts to resolve vulnerabilities.

Results:

  • Major update to grunt version from 0.4.1 to 1.0.3
  • Minor update to jshint from 2.8.0 to 2.9.6
  • Major update to mocha from 2.3.4 to 5.2.0

After these updates:

  • Running grunt resulted in success message of 3 files php linted for both tasks.
  • Running npm test resulted in 1/1 passing tests.

Would appreciate any feedback. I see this PR #30 was closed and couldn't find an explanation for why.

Ran npm audit fix and followed prompts to resolve vulnerabilities.

Results:
- Major update to grunt version from 0.4.1 to 1.0.3
- Minor update to jshint from 2.8.0 to 2.9.6
- Major update to mocha from 2.3.4 to 5.2.0
@toddmilliken
Copy link
Author

@jgable no rush on this 😄 , just wondering if this is still being maintained. There's only a few repositories I use that leverage grunt-phplint

@toddmilliken
Copy link
Author

Closing due to repo inactivity

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

Successfully merging this pull request may close these issues.

None yet

1 participant