Babel's modular runtime helpers that provide transpilation support for modern JavaScript features
94
{
"context": "This criteria evaluates the engineer's ability to use @babel/core's loadPartialConfig API to inspect Babel configuration. The focus is on correct usage of loadPartialConfig (or its async/sync variants), proper extraction of configuration metadata, and appropriate handling of cases where no configuration exists.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses loadPartialConfig",
"description": "Uses loadPartialConfig, loadPartialConfigAsync, or loadPartialConfigSync from @babel/core to load configuration instead of loadOptions or other APIs.",
"max_score": 30
},
{
"name": "Accesses config paths",
"description": "Correctly accesses the configuration file paths from the result, including config, babelrc, and ignore properties from the returned PartialConfig object.",
"max_score": 25
},
{
"name": "Extracts options property",
"description": "Correctly extracts and returns the options property from the PartialConfig result, which contains resolved Babel options including plugins and presets.",
"max_score": 20
},
{
"name": "Handles null result",
"description": "Properly handles the case when loadPartialConfig returns null (no configuration found) by returning null or appropriate indication.",
"max_score": 15
},
{
"name": "Uses hasFilesystemConfig",
"description": "Accesses and includes the hasFilesystemConfig boolean property from the PartialConfig result to indicate whether configuration was loaded from filesystem.",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-babel--runtimedocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10