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

is this still maintained? #100

Open
graingert opened this issue Oct 19, 2017 · 7 comments
Open

is this still maintained? #100

graingert opened this issue Oct 19, 2017 · 7 comments

Comments

@graingert
Copy link

@zaach ^

@graingert
Copy link
Author

@zaach this project is now broken: npm/npm#19875

@realityking
Copy link

See #103

@Berkmann18
Copy link

@graingert Seems like it.

@prantlf
Copy link

prantlf commented May 12, 2019

Try the NPM module paulvollmer/jsonlint from Paul Vollmer's fork.

  • It uses the new and maintained nomnom package to avoid audit problems.
  • It fixes command-line parsing so that you can pass multiple files or use wildcards.

@Berkmann18
Copy link

@prantlf Just tried that one and I still get the warning.

@prantlf
Copy link

prantlf commented May 17, 2019

@Berkmann18, you're right, sorry. Audit reports no problems, but the package deprecation is reported as a non-fatal warning:

npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.

@prantlf
Copy link

prantlf commented May 18, 2019

I needed some bugfixes and extensions to jsonlint and did them in my fork. I released the changes as a new NPM module @prantlf/jsonlint. Replacing the deprecated nomnom with commander in the package dependencies was one of them.

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

No branches or pull requests

4 participants