-
-
Notifications
You must be signed in to change notification settings - Fork 18
Conversation
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.
We should generally classify scripts as build, release, lint, start, or test.
package.json
Outdated
"build": "npm run bundle && npm run tsc", | ||
"build:debug": "npm run bundle -- -m && npm run tsc", | ||
"build:keys": "node tools/build-keys-from-ts", | ||
"bundle": "rollup -c", | ||
"coverage": "c8 report --reporter lcov && opener coverage/lcov-report/index.html", |
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.
Not sure about this one, maybe test:open-coverage
?
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.
Makes sense.
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.
LGTM, thanks! Would like @nzakas to verify before merging. I can update Jenkins script after we merge this.
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.
LGTM. Thanks.
Updated. |
Prerequisites checklist
What is the purpose of this pull request?
Refers eslint/eslint#14827
What changes did you make? (Give an overview)
This updates the names of the scripts in package.json to be consistent with the new standard.
Is there anything you'd like reviewers to focus on?
We may need to update the
release
related scripts on Jenkins before merging this PR.