@oclif/plugin-warn-if-update-available

warns if there is a newer version of CLI released

• @oclif/plugin-warn-if-update-available
• What is this?
• How it works
• Installation
• Configuration
• Environment Variables
• Contributing

What is this?

This plugin shows a warning message if a user is running an out of date CLI.

How it works

This checks the version against the npm registry asynchronously in a forked process once every 60 days by default (see Configuration for how to configure this). It then saves a version file to the cache directory that will enable the warning. The upside of this method is that it won't block a user while they're using your CLI—the downside is that it will only display after running a command that fetches the new version.

Installation

Add the plugin to your project with yarn add @oclif/plugin-warn-if-update-available, then add it to the package.json of the oclif CLI:

1{
2  "name": "mycli",
3  "version": "0.0.0",
4  // ...
5  "oclif": {
6    "plugins": ["@oclif/plugin-help", "@oclif/plugin-warn-if-update-available"]
7  }
8}

Configuration

In package.json, set oclif['warn-if-update-available'] to an object with any of the following configuration properties:

• timeoutInDays - Duration between update checks. Defaults to 60.
• message - Customize update message.
• registry - URL of registry. Defaults to following your .npmrc configuration
• authorization - Authorization header value for registries that require auth. Defaults to following your .npmrc configuration
• frequency - The frequency that the new version warning should be shown.
• frequencyUnit - The unit of time that should be used to calculate the frequency (days, hours, minutes, seconds, milliseconds). Defaults to minutes.

Example configuration

1{
2  "oclif": {
3    "plugins": ["@oclif/plugin-warn-if-update-available"],
4    "warn-if-update-available": {
5      "timeoutInDays": 7,
6      "message": "<%= config.name %> update available from <%= chalk.greenBright(config.version) %> to <%= chalk.greenBright(latest) %>.",
7      "registry": "https://my.example.com/module/registry",
8      "authorization": "Basic <SOME READ ONLY AUTH TOKEN>"
9    }
10  }
11}

Notification Frequency

Once a new version has been found, the default behavior is to notify the user on every command execution. You can modify this by setting the frequency and frequencyUnit options.

Examples

Once every 10 minutes.

1{
2  "oclif": {
3    "warn-if-update-available": {
4      "frequency": 10
5    }
6  }
7}

Once every 6 hours.

1{
2  "oclif": {
3    "warn-if-update-available": {
4      "frequency": 6,
5      "frequencyUnit": "hours"
6    }
7  }
8}

Once a day.

1{
2  "oclif": {
3    "warn-if-update-available": {
4      "frequency": 1,
5      "frequencyUnit": "days"
6    }
7  }
8}

Once every 30 seconds.

1{
2  "oclif": {
3    "warn-if-update-available": {
4      "frequency": 30,
5      "frequencyUnit": "seconds"
6    }
7  }
8}

Environment Variables

• <CLI>_SKIP_NEW_VERSION_CHECK: Skip this version check
• <CLI>_FORCE_VERSION_CACHE_UPDATE: Force the version cache to update
• <CLI>_NEW_VERSION_CHECK_FREQ: environment variable override for frequency setting
• <CLI>_NEW_VERSION_CHECK_FREQ_UNIT: environment variable override for frequencyUnit setting

Contributing

See contributing guide