Authentication for Private npm Registries¶

If you make use of private npm registries, you can set-up the necessary credentials in your configuration.

Tip: We recommend to keep the credentials in the website configuration only, and not add them to your .scrutinizer.yml in your repository so that they do not become part of your repository history.

Using the Default Registry¶

build:
  environment:
    node:
      version: v6.2.0
      npm:
        # Login to https://registry.npmjs.org/
        username: some-username
        password: s3cret-password
        email: [email protected]

Using a Custom Private Registry¶

build:
  environment:
    node:
      version: v6.2.0
      npm:
        registries:
          - username: some-username
            password: s3cret-password
            email: [email protected]
            url: http://myregistry.example.com
            scope: myscope
            always_auth: true

          - username: some-username
            password: s3cret-password
            email: [email protected]
            url: http://myregistry.another-example.com
            scope: myscope
            always_auth: true