CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/npm-aggregate-error

Create an error from multiple errors

94

1.28x
Quality

Pending

Does it follow best practices?

Impact

94%

1.28x

Average score across 9 eval scenarios

SecuritybySnyk

Pending

The risk profile of this skill

Overview
Eval results
Files

criteria.jsonevals/scenario-1/

{
  "context": "This evaluation criteria assesses how well the engineer uses the aggregate-error package to normalize different error-like inputs (Error instances, plain objects, and strings) into standard Error instances. The focus is on correct usage of the package's error normalization capabilities.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses aggregate-error package",
      "description": "The implementation imports and uses the aggregate-error package (via require or import statement)",
      "max_score": 15
    },
    {
      "name": "Error instance preservation",
      "description": "Uses AggregateError to preserve existing Error instances without modification (tests show Error instances remain identical after normalization)",
      "max_score": 25
    },
    {
      "name": "Object to Error conversion",
      "description": "Uses AggregateError's capability to convert plain objects with message properties to Error instances while preserving metadata properties (like code, statusCode, etc.)",
      "max_score": 25
    },
    {
      "name": "String to Error conversion",
      "description": "Uses AggregateError's capability to wrap string values in Error instances with the string as the error message",
      "max_score": 20
    },
    {
      "name": "Access normalized errors",
      "description": "Correctly uses the AggregateError.errors property or getter to access the normalized error array",
      "max_score": 15
    }
  ]
}

tile.json