不要怂,就是干,撸起袖子干!

Commit c902b076 by Felix Becker

chore(scripts): don't run lint as part of npm test

- npm run lint was run twice in CI
- npm test was not doing the same as npm run cover
- linting does not need to be run on AppVeyor, there was a weird bug on Windows Node 4 + ESLint
1 parent 2fc43c4c
Showing with 1 additions and 1 deletions
...@@ -99,7 +99,7 @@ ...@@ -99,7 +99,7 @@
"main": "index", "main": "index",
"scripts": { "scripts": {
"lint": "eslint lib test --quiet", "lint": "eslint lib test --quiet",
"test": "npm run lint && npm run teaser && npm run test-unit && npm run test-integration", "test": "npm run teaser && npm run test-unit && npm run test-integration",
"test-docker": "npm run test-docker-unit && npm run test-docker-integration", "test-docker": "npm run test-docker-unit && npm run test-docker-integration",
"test-docker-unit": "env-cmd ./test/config/.docker.env npm run test-unit", "test-docker-unit": "env-cmd ./test/config/.docker.env npm run test-unit",
"test-docker-integration": "env-cmd ./test/config/.docker.env npm run test-integration", "test-docker-integration": "env-cmd ./test/config/.docker.env npm run test-integration",
......
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!