Update notifications for your CLI app
Overall
score
97%
{
"context": "This criteria evaluates how well the engineer uses update-notifier's semantic version intelligence and comparison features to build a version status reporter. The focus is on proper usage of the package's API for fetching version information, accessing update metadata, and utilizing the semantic version comparison capabilities.",
"type": "weighted_checklist",
"checklist": [
{
"name": "UpdateNotifier instantiation",
"description": "Correctly creates an UpdateNotifier instance using updateNotifier() factory function with required pkg.name and pkg.version options",
"max_score": 15
},
{
"name": "fetchInfo() method usage",
"description": "Uses the fetchInfo() method to programmatically retrieve update information from npm registry instead of relying on automatic background checks",
"max_score": 25
},
{
"name": "Update object access",
"description": "Accesses and utilizes the update information object returned by fetchInfo() or available via notifier.update property, extracting latest, current, type, and name fields",
"max_score": 20
},
{
"name": "Update type classification",
"description": "Correctly uses the 'type' field from the update information to determine the semantic version difference (major, minor, patch, prerelease, build, or latest)",
"max_score": 20
},
{
"name": "Version comparison logic",
"description": "Properly determines whether an update is needed by checking if the update object exists and comparing current vs latest versions using update-notifier's built-in semantic version intelligence",
"max_score": 15
},
{
"name": "Async/Promise handling",
"description": "Correctly handles the asynchronous nature of fetchInfo() using async/await or Promise chains",
"max_score": 5
}
]
}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