Update notifications for your CLI app
Overall
score
97%
{
"context": "This criteria evaluates how well the engineer uses the update-notifier package to implement non-blocking update detection via background processes. It focuses on proper usage of the package's core API for background checking, state persistence, and notification display.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Package initialization",
"description": "Correctly imports and initializes update-notifier with the updateNotifier() factory function, passing a configuration object with pkg.name and pkg.version properties",
"max_score": 15
},
{
"name": "Background check invocation",
"description": "Uses the check() method or relies on automatic checking triggered by the updateNotifier() factory to initiate background update checks without blocking execution",
"max_score": 25
},
{
"name": "Update notification display",
"description": "Uses the notify() method to display update notifications when updates are available, allowing the package to handle the formatting and display logic",
"max_score": 20
},
{
"name": "Check interval configuration",
"description": "Configures updateCheckInterval option (in milliseconds) to control the frequency of update checks and avoid redundant API calls",
"max_score": 15
},
{
"name": "State persistence",
"description": "Leverages update-notifier's built-in ConfigStore-based persistence for storing update information and check timestamps, accessing via the config property or update property as needed",
"max_score": 15
},
{
"name": "Proper API integration",
"description": "Integrates update-notifier correctly into the module's public API, returning or exposing the necessary methods (check, notify) through the createVersionMonitor function as specified",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-update-notifierdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10