This starts the linting process (npm run lint) explicitly in the CI test pipeline because the implicit lint call in the npm run test command does not break the pipeline, even if there are linting errors. So possible linting errors land in the Wegue code base if not discovered by human reviewers, which leads to a broken build.
This starts the linting process (
npm run lint
) explicitly in the CI test pipeline because the implicit lint call in thenpm run test
command does not break the pipeline, even if there are linting errors. So possible linting errors land in the Wegue code base if not discovered by human reviewers, which leads to a broken build.