🐛 after running check --apply, vue files become empty

[Jungzl]

Environment information

CLI:
  Version:                      1.7.0
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         unset
  JS_RUNTIME_VERSION:           "v20.12.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

2024-04-15.23-41-53.mp4

Expected result

It should works as usual

Code of Conduct

• I agree to follow Biome's Code of Conduct

[ematipico]

Any chance we could have a reproduction?

[Jungzl]

It's just vite start template with biome

[Jungzl]

BTW I'm using biome plugin in WebStorm, if I don't check this option, the error won't occur.

And running script like pnpm biome check --apply . is just ok, maybe related to plugin?

[Jungzl]

Can confirm that in VSCode, it's fine.

[ematipico]

Yeah I think it's related to plugin

[kujtimiihoxha]

Seeing the same issue also

[tasshi-me]

Hello, there!
I see the same issue with Astro files.

This issue seems to be caused by biomejs/biome#2225.
For Vue or Astro files, the biome CLI with the --stdin-file-path option will output nothing with a zero status code.
This plugin writes the output of the CLI command, so the src file is overwritten by empty string.

Reproduction

I enabled only the "Run safe fixes on save" option.

This plugin runs biome CLI inside, so I tried a command that is generated by this plugin on my local shell.
The result of this command is written to the src file.

$ [node path] [biome path] check --stdin-file-path [src path] --formatter-enabled=false --apply --config-path [config path]

This plugin passes the source code to the stdin of the above command.

$ cat [src path] | [node path] [biome path] check --stdin-file-path [src path] --formatter-enabled=false --apply --config-path [config path]

For a TypeScript (.ts) file

It prints formatted code. The status code is zero.

$ cat /path/to/project/src/consts.ts |\
    /Users/user/.nodenv/shims/node \
    /path/to/project/node_modules/@biomejs/biome/bin/biome check \
    --stdin-file-path /path/to/project/src/consts.ts \
    --formatter-enabled=false --apply \
    --config-path /path/to/project
... # (The formatted code is printed)

$ echo $?
0

For a Astro (.astro) file

It prints nothing. The status code is zero.

$ cat /path/to/project/src/pages/index.astro |\
    /Users/user/.nodenv/shims/node \
    /path/to/project/node_modules/@biomejs/biome/bin/biome check \
    --stdin-file-path /path/to/project/src/pages/index.astro \
    --formatter-enabled=false --apply \
    --config-path /path/to/project
# (Nothing printed)

$ echo $?
0

[tasshi-me]

In the VSCode plugin, this issue does not happen because the architecture seems to be different.
(Sorry, I don't know well.)

• https://github.com/biomejs/biome-vscode/blob/b55af94cb26f4c86c2213db93ccf6982e17ec0e2/src/main.ts#L175
• https://speakerdeck.com/unvalley/typescript-linnting-and-formatting?slide=12