Update notifications for your CLI app
npm install update-notifier-webpack> webpack-compliant update notifications for your CLI app
Not limited to but including webpack support
among other bundlers.
#### Contents
- Install
- Typescript
- Usage
- How
- API
- About
It's a fork of update-notifier that has been created
due to original package current and future incompatibility
with bundlers such as webpack.
``
$ npm install update-notifier-webpack
`vue`
$ npm install -D @types/update-notifier-webpack@npm:@types/update-notifier
`js
const updateNotifier = require('update-notifier-webpack');
const pkg = require('./package.json');
updateNotifier({pkg}).notify();
`
`js
const updateNotifier = require('update-notifier-webpack');
const pkg = require('./package.json');
// Checks for available update and returns an instance
const notifier = updateNotifier({pkg});
// Notify using the built-in convenience method
notifier.notify();
// notifier.update contains some useful info about the update`
console.log(notifier.update);
/*
{
latest: '1.0.1',
current: '1.0.0',
type: 'patch', // Possible values: latest, major, minor, patch, prerelease, build
name: 'pageres'
}
*/
`js
const notifier = updateNotifier({
pkg,
updateCheckInterval: 1000 60 60 24 7 // 1 week
});
if (notifier.update) {
console.log(Update available: ${notifier.update.latest});`
}
Whenever you initiate the update notifier and it's not within the interval threshold, it will asynchronously check with npm in the background for available updates, then persist the result. The next time the notifier is initiated, the result will be loaded into the .update property. This prevents any impact on your package startup performance.process.exit
The update check is done in a unref'ed child process. This means that if you call , the check will still be performed in its own process.
The first time the user runs your app, it will check for an update, and even if an update is available, it will wait the specified updateCheckInterval before notifying the user. This is done to not be annoying to the user, but might surprise you as an implementer if you're testing whether it works. Check out example.js to quickly test out update-notifier and see how you can test that it works in your app.
Checks if there is an available update. Accepts options defined below. Returns an instance with an .update property if there is an available update, otherwise undefined.
Type: object
#### pkg
Type: object
##### name
Required\
Type: string
##### version
Required\
Type: string
#### updateCheckInterval
Type: number\1000 60 60 24
Default: (1 day)*
How often to check for updates.
#### shouldNotifyInNpmScript
Type: boolean\false
Default:
Allows notification to be shown when running as an npm script.
#### distTag
Type: string\'latest'
Default:
Which dist-tag to use to find the latest version.
Check update information.
Returns an object with:
- latest _(String)_ - Latest version.current
- _(String)_ - Current version.type
- _(String)_ - Type of current update. Possible values: latest, major, minor, patch, prerelease, build.name
- _(String)_ - Package name.
Convenience method to display a notification message. (See screenshot)
Only notifies if there is an update and the process is TTY.
#### options
Type: object
##### defer
Type: boolean\true
Default:
Defer showing the notification to after the process has exited.
##### message
Type: string\
Default: See above screenshot
Message that will be shown when an update is available.
Available placeholders:
- {packageName} - Package name.{currentVersion}
- - Current version.{latestVersion}
- - Latest version.{updateCommand}
- - Update command.
`js{updateCommand}
notifier.notify({message: 'Run to update.'});
// Output:
// Run npm install update-notifier-tester@1.0.0 to update.`
##### isGlobal
Type: boolean\
Default: Auto-detect
Include the -g argument in the default message's npm i recommendation. You may want to change this if your CLI package can be installed as a dependency of another project, and don't want to recommend a global installation. This option is ignored if you supply your own message (see above).
##### boxenOptions
Type: object\{padding: 1, margin: 1, align: 'center', borderColor: 'yellow', borderStyle: 'round'}
Default: (See screenshot)
Options object that will be passed to boxen.
Users of your module have the ability to opt-out of the update notifier by changing the optOut property to true in ~/.config/configstore/update-notifier-[your-module-name].json. The path is available in notifier.config.path.
Users can also opt-out by setting the environment variable NO_UPDATE_NOTIFIER with any value or by using the --no-update-notifier flag on a per run basis.
The check is also skipped automatically:
- on CI
- in unit tests (when the NODE_ENV environment variable is test`)
The idea for this module came from the desire to apply the browser update strategy to CLI tools, where everyone is always on the latest version. We first tried automatic updating, which we discovered wasn't popular. This is the second iteration of that idea, but limited to just update notifications.
There are a bunch projects using it:
- npm - Package manager for JavaScript
- Yeoman - Modern workflows for modern webapps
- AVA - Simple concurrent test runner
- XO - JavaScript happiness style linter
- Node GH - GitHub command line tool
---