Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No stack traces on error #29

Open
ckeeney opened this issue Apr 18, 2022 · 0 comments
Open

No stack traces on error #29

ckeeney opened this issue Apr 18, 2022 · 0 comments

Comments

@ckeeney
Copy link

ckeeney commented Apr 18, 2022

When a command throws an error, the error message prints to the console but not the full stack trace. This makes development very difficult.

Example:

// ./commands/debug.js

const anotherFunction = () => {
    throw Error("you can't find me.")
}

const aFunction = () => {
    anotherFunction();
}

export default async function debug() {
    aFunction();
}

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant