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

feat: add package.json linter #304

Merged
merged 3 commits into from
Dec 17, 2018
Merged

Conversation

hugomrdias
Copy link
Member

This PR adds package.json linting with npm-package-json-lint and config for it.
Check this issue #303 for context about these changes, not all issues are solve in this PR but still improves the current situation.

//cc @ipfs/javascript-team

@ghost ghost assigned hugomrdias Dec 4, 2018
@ghost ghost added the status/in-progress In progress label Dec 4, 2018
src/config/.npmpackagejsonlintrc.json Outdated Show resolved Hide resolved
@jacobheun
Copy link
Contributor

What do you think about adding "pre-push": ["lint"] checking logic to this? Linting is pretty quick to run locally and I think we should start enforcing it before pushes. Not having to run CI again because we missed something in linting would probably save us quite a bit of CI runtime.

@hugomrdias
Copy link
Member Author

i'm preparing another PR about git hooks to handle that and more. But im waiting for an automated way to overwrite the current git-validate we all have in our local repos.

Copy link
Contributor

@jacobheun jacobheun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! 🚀

Copy link
Member

@achingbrain achingbrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hugomrdias hugomrdias merged commit f90bd78 into master Dec 17, 2018
@ghost ghost removed the status/in-progress In progress label Dec 17, 2018
@hugomrdias hugomrdias deleted the feat/add-lint-package-json branch December 17, 2018 23:53
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.

3 participants