-
Notifications
You must be signed in to change notification settings - Fork 28
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
standard #23
standard #23
Conversation
Shoot; pulled in something from another branch. Lemme revert it out of this PR. |
This reverts commit b37267b.
@@ -4,7 +4,7 @@ | |||
"description": "Quick and simple deploy tool to host Native Web Applications and Static Web Pages in IPFS", | |||
"bin": "bin.js", | |||
"scripts": { | |||
"test": "echo \"Error: no test specified\" && exit 1" | |||
"test": "standard" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
following the style of other js projects, we do "lint": "standard"
and reserve the test keyword for tests.
for pre-commit hook, we use pre-commit and add to the package.json
pre-commit: [
"lint",
"test", // <- if any
"coverage" // <- if any
]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! I like keeping "lint" and "test" more explicitly divided.
Is there a style guide somewhere for JS IPFS projects?
Thank you @noffle :D @RichardLitt is working on the js guidelines ipfs/community#92 |
@diasdavid we're all working on the js guidelines. :) I'm just putting it into a readme. |
ipscend
is already using StandardJS -- this just adds it tonpm test
. It'd also work as a pre-commit hook though.