---
tasks:
  ubuntu1804:
    shell_commands:
      # Buildkite expects to be able to build at least one target, so we create
      # a dummy workspace here.
      - echo 'workspace(name = "build_bazel_vscode_bazel_dummy")' > WORKSPACE
      - echo 'filegroup(name = "dummy")' > BUILD
      # Install node_modules and then check the code for lint errors.
      - npm install
      - npm run check-lint
      # TODO(allevato): Add a prettier check to verify that *.ts files don't
      # differ from their prettier output. We need `prettier-tslint` so that
      # prettier will obey our tslint config, but it doesn't support
      # Typescript 3 yet.
      # (https://github.com/azz/prettier-tslint/issues/18)
    build_targets:
      - "//:dummy"

---
tasks:
  ubuntu1804:
    shell_commands:
      # Buildkite expects to be able to build at least one target, so we create
      # a dummy workspace here.
      - echo 'workspace(name = "build_bazel_vscode_bazel_dummy")' > WORKSPACE
      - echo 'filegroup(name = "dummy")' > BUILD
      # Install node_modules and then check the code for lint errors.
      - npm ci
      - npm run check-lint
      # TODO(allevato): Add a prettier check to verify that *.ts files don't
      # differ from their prettier output. We need `prettier-tslint` so that
      # prettier will obey our tslint config, but it doesn't support
      # Typescript 3 yet.
      # (https://github.com/azz/prettier-tslint/issues/18)
    build_targets:
      - "//:dummy"

Use `npm ci` (clean-install) for CI.
Use `npm ci` (clean-install) for CI.

Looking at `npm help ci` it seems like CI setups are better off using it (vs.
`install`) because it won't try to update the package json files.

Note: `clean-install` exists also exists in newer npm versions, but the npm
version on the BazelCI machines doesn't seem to include it.

Use 'ci' instead of 'clean-install'
