A zero-dependency alternative to cosmiconfig for loading configuration files
89
{
"context": "This evaluation assesses the engineer's ability to properly use lilconfig's synchronous API (lilconfigSync) for configuration file search, loading, and cache management. The focus is on correct usage of the lilconfigSync function and its associated methods.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses lilconfigSync function",
"description": "The implementation correctly imports and calls the lilconfigSync() function to create a synchronous configuration explorer, rather than using the async lilconfig() function.",
"max_score": 25
},
{
"name": "Implements search method",
"description": "The findConfig function correctly uses the search() method from the lilconfigSync explorer to search for configuration files, passing the searchFrom parameter and returning the result.",
"max_score": 25
},
{
"name": "Implements load method",
"description": "The loadConfig function correctly uses the load() method from the lilconfigSync explorer to load a specific configuration file by path and return the result.",
"max_score": 25
},
{
"name": "Implements cache clearing",
"description": "The clearCache function correctly uses the clearCaches() method (or clearSearchCache() and clearLoadCache()) from the lilconfigSync explorer to clear cached configuration data.",
"max_score": 15
},
{
"name": "Correct explorer initialization",
"description": "The lilconfigSync explorer is initialized with an appropriate configuration name (e.g., 'myapp') and the explorer instance is reused across function calls rather than creating a new explorer for each operation.",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-lilconfigdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10