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

deno fmt crash #26858

Open
ericfrederich opened this issue Nov 13, 2024 · 0 comments
Open

deno fmt crash #26858

ericfrederich opened this issue Nov 13, 2024 · 0 comments

Comments

@ericfrederich
Copy link

Version:

deno 2.0.6 (stable, release, x86_64-unknown-linux-gnu)
v8 12.9.202.13-rusty
typescript 5.6.2

I created a new backstage app via npx @backstage/create-app@latest and tried to run deno fmt against it and it exits with code 137 and prints "Killed"

It was a chore trying to find out exactly which file was causing the error but it was .yarn/releases/yarn-4.4.1.cjs

I'm writing this one as a bug because deno crashes but feel like there could also be a couple of feature requests that come from this as well. Rather than preemptively creating them and generating noise I'll leave them here for discussion. If they look good feel free to create new Bug issues out of them linking back here.

deno fmt doesn't identify the file it fails on

Not entirely sure where the Killed message is coming from, but if deno knows which file caused an error it should be printed to the console.

To find the file causing problems I had to run this:

for fname in $(git ls-tree -r HEAD --name-only); do echo $fname; deno fmt $fname; done

Perhaps a --verbose flag could help as well rather than leaving users in the dark or resorting to something like the above script.

option to piggy-back on //prettier-ignore

Perhaps not by default, but maybe there should be an option to ignore files with //prettier-ignore as well as // deno-fmt-ignore-file

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