Skip to content

feat: print full stack trace on error #3142

@tmillr

Description

@tmillr
  • What you're trying to do
    Debug my code.

  • Why you can't use AVA for this
    No stack trace on error? Only error message is printed.

  • And maybe how you think AVA could handle this
    Print full stack trace on error so that I can find out where they are occurring, including when they occur within async fn's. Or, at the very least make it opt-in.

Things can get really painful when errors occur and there's only an error message but no stack trace. I'm not sure if this is something specific to async functions and/or specific to AVA, but it can get pretty annoying when rapidly prototyping with vanilla JS. Is this the expected behavior? Or maybe I've messed something up?

Screen Shot 2022-11-26 at 4 46 17 AM

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions