Replies: 1 comment
-
You can achieve that via standard input: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Biome attempts to determine the file format based on the file extension. This covers most cases but not all - extensions can be non-standard or may be completely absent. For example, when using the override function in Chrome and Firefox, the browser creates a file with a name that SHOULD correspond to the path from which this file was obtained
For instance,
./header.js?adTagId=8.
Although I can manually specify for the editor that this is a JavaScript file by selecting the format, Biome in this case cannot format it. The error message contains the following:
Steps and logs
The simplest way to reproduce the issue is to try to format such a file via the command line:
Possible solution:
Add a parameter to manually specify the file format by indicating the associated extension, for example:
$ npx @biomejs/biome format --write "./header.js?adTagId=8" --lang=js
Beta Was this translation helpful? Give feedback.
All reactions