☂️ Road to Biome v2.0

[ematipico]

Tasks

We will use this issue to track all the necessary breaking changes and removal of deprecation we plan to do for the next major of Biome.

Biome related

• BREAKING: Remove support for rome.json #4243
• BREAKING: Remove support for suppression comments rome-ignore #4251
• BREAKING: Remove the deprecated trailingComma option #4256
• BREAKING: Remove the deprecated --apply CLI option #4267
• BREAKING: Remove the deprecated BIOME_LOG_DIR #4288
• BREAKING: Remove the deprecated support of root_path from the LSP @nhedger
• BREAKING: Remove the deprecated indentSize option #4269
• BREAKING: Remove deprecated rules #4767
• 📎 Support {a,b} glob pattern syntax for includes/excludes #2986
• 📎 Remove undocumented values for CLI options #3619
• Resolve configuration paths/globs from the configuration, instead of from the working directory #4813
• Enable .editorconfig support by default #4812
• 📎 Monorepo support #2228
• Make https://biomejs.dev/linter/rules/use-exhaustive-dependencies/ not recommended #4293
• Move useWhile from style to complexity. #4776
• 📎 biome <command> should behave identically to biome <command> ./ #3946
• 📎 Refactor/fix JsParserSettings for better override behavior #3297
• Revisit our versioning philosophy? A major is the best time to do that.
• BREAKING: don't parse JSX in .js and .ts files #4385
• Add option to parse JSX in .js and .ts files #4716
• Remove dynamic regex (RegExep("", "")) support in regex-related rules (noControlCharacterInRegex and noMisleadingCharacterClass)
• Rename some rules. This could be made in a backward compatible way by keeping the old rule as deprecated.
  - noMultipleSpacesInRegularExpressionLiterals -> noMultipleSpacesInRegex
  - noUnusedTemplateLiteral -> noUselessTemplateLiteral?
• Think about adopting the same defaults as Prettier for our options to make migration easier. Notably, indentStyle.
• 📎 turn on requireAscii by default #1918
• vcs.useIgnoreFile ignores nested ignore files #2312
• 📎 include should prevent Biome of traversing non-included directories #2000
• Format package.json like Prettier does, by default #4370
• BREAKING: change workspace fields camel case e.g. skipped_diagnostics -> skippedDiagnostics #4366
• 💅 lint/a11y/useAltText asks for alt when using object spread #3977
  BREAKING
• BREAKING Remove parsing support for assert {} #4359
• Rename biome_rowan methods #4296
• Analyzer top-level suppressions #4305
• Analyzer range suppressions #4569
• BREAKING: don't exit with an error for max limit files #4375
• Implement plugin loading in the workspace server #4832
• 📎 Multi-file support #3307
• Revamp analyzer diagnostic system #4626
• ☂️ Revamp linter #4662
• 📎 Implement suppression of plugin diagnostics #4667
• 📎 Clean up WorkspaceError #4668
• Emit a warning when biome.json and biome.jsonc are located in the same folder #4936
• Remove support for arbitrary extension for --config-path and BIOME_CONFIG_PATH. We should handle only .json and .jsonc and emit an error otherwise. #4942
• Make organizeImports a full-fledged assist action
• Remove support for max_line_length from editorconfig #4892

Infrastructure and community related

These tasks are for the great Biome community and infrastrcture.

• Use knope for automated release process
• Create a chat.biomejs.dev sub-domain, create a redirect to the discord invite link, and change all the occurrences to use chat.biomejs.dev

Developments

• For anyone who has the right to modify the issue, please add additional tasks to the list.
• We plan to merge changes to the next branch, and regularly rebase main into next until we reach a point where we can merge next into main.
• We will regularly rebase main into next. Please DOT NOT USE git merge. Please use git rebase
• For anyone involved in the developments, please enable git rerere for your sanity. This feature will cache all the conflict resolutions on your local machine, so next time you happen to have the same resolution, git will apply it automatically. Very useful when rebasing the same branch.
• Create an issue every time you start working on something, so GitHub will automatically automate the workflow (it will tick the checkbox once the issue is closed).

Engagements with this issue

If possible, please refrain from commenting on this issue unless you're involved with the developments. If you want to discuss a decision, please use the relative issue. If an issue doesn't exist, please use Discord, or wait for an issue to be open.

[ematipico]

I removed the task to rethinking formatter defaults. While I understand the motivation, there's no need. There's the option, so discussing defaults is just... bike-shedding.

[lcswillems]

Why @ematipico is it back-shedding? Personally, each time I'm trying to replace eslint / prettier by Biome, there is a bunch of settings I need to set (the main one being to use spaces instead of tabs). If the defaults were different, I would not need to do this?

[ematipico]

@lcswillems I don't want to spur a discussion from here, so if you have some options, please create one. To answer your question, it's essentially impossible to have perfect defaults because people have opinions that differ from one to another. It all comes down to "De gustibus", where every opinion is legit but not a correct one.

So, instead of focusing our (the team's and yours, the user's) energies on discussing which default "is correct", we should discuss the presence of options which are more productive for all parties.

If defaults are different, they would help your, but they might affect other users. We can make the on-boarding easier, but there's always a party that might be discontent, which ties up to the beginning of the discussion.

[lcswillems]

Hey @ematipico, thanks for your answer!

It is indeed not possible to find a default that is optimal for each and every user. But it doesn't mean that there is not a default that is better than another overall, while considering the group of users.

If the defaults in Biome were chosen randomly, it would be a nightmare to use Biome. Same thing for all the tools that we use in our daily life.

The reason I took my personal example was just because I believe that all the people migrating from eslint / prettier would be in my situation (and so maybe a lot of users). And so I felt it was important to keep in mind.

At the end of the day, I can understand that it might be low priority and not worth prioritizing for v2.0 or any release. But I don't think we should conclude that caring about the defaults is not important and that all the defaults are equivalent.

[ematipico]

And that's why biome migrate prettier and biome migrate eslint were created