SvelteKit adapter that automatically detects deployment environment and installs appropriate platform-specific adapter
Overall
score
96%
{
"context": "This criteria evaluates how well an engineer uses the @sveltejs/adapter-auto package's peer dependency resolution patterns to implement a package resolver utility. The focus is on correctly implementing scope parsing, directory traversal, and package.json export resolution.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Scope name parsing",
"description": "Correctly splits scoped package names (e.g., @scope/name) from the dependency string by detecting the @ prefix and splitting on / to extract both scope and package name components",
"max_score": 20
},
{
"name": "Directory traversal logic",
"description": "Implements upward directory traversal using path.dirname() or similar to search parent directories for node_modules, continuing until the package is found or reaching the filesystem root",
"max_score": 25
},
{
"name": "Package.json reading",
"description": "Reads and parses the package.json file using fs.readFileSync() and JSON.parse() to access the exports field for subpackage resolution",
"max_score": 20
},
{
"name": "Export path resolution",
"description": "Resolves package.json exports by extracting the subpackage path, looking it up in the exports object, and handling nested conditions (import/default) to determine the final export path",
"max_score": 25
},
{
"name": "Error handling",
"description": "Throws appropriate errors when packages cannot be found in the node_modules hierarchy or when specified exports don't exist in package.json",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-sveltejs--adapter-autodocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10