You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
forfnamein$(git ls-tree -r HEAD --name-only);doecho$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
The text was updated successfully, but these errors were encountered:
Version:
I created a new backstage app via
npx @backstage/create-app@latest
and tried to rundeno fmt
against it and it exits with code137
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:
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
The text was updated successfully, but these errors were encountered: