☂️ 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

• [x] #4243
• [x] #4251
• [x] #4256
• [x] #4267
• [x] #4288
• [x] BREAKING: Remove the deprecated support of root_path from the LSP @nhedger
• [x] #4269
• [ ] BREAKING: Remove deprecated rules (noInvalidNewBuiltin, noNewSymbol, useShorthandArrayType, useSingleCaseStatement, noConsoleLog)
• [ ] #2986
• [x] #3619
• [ ] Resolve configuration paths/globs from the configuration, instead from the working directory
• [ ] Enable .editorconfig support by default
• [ ] #2228
• [x] #4293
• [ ] Move useWhile from style to complexity.
• [ ] #3946
• [ ] #3297
• [ ] Revisit our versioning philosophy? A major is the best time to do that.
• [ ] #4385
• [ ] Add option to parse JSX in .js and .ts files
• [ ] 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.
• [ ] https://github.com/biomejs/biome/issues/1918
• [ ] https://github.com/biomejs/biome/issues/2312
• [ ] https://github.com/biomejs/biome/issues/2000
• [ ] #4370
• [x] #4366
• [ ] https://github.com/biomejs/biome/issues/3977 BREAKING
• [x] #4359
• [ ] Introduce a JSON formatter option that expands JSON object/array (aka lineWidth: 1)?
• [x] #4296
• [x] #4305
• [x] #4569
• [x] #4375
• [ ] Implement plugin loading in the workspace server
• [ ] #3307
• [ ] #4626
• [ ] #4662
• [ ] #4667
• [x] #4668

Infrastructure and community related

These tasks are for the great Biome community and infrastrcture.

• [ ] Use knope for automated release process
• [x] 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.

[akkadaya]

I'm new to the Biome project, I came here out of frustration from configuring ESLint in a mono-repo.

What does this mean? are trailingComma not allowed anymore?

Remove the deprecated trailingComma option

Again, I'm new and I haven't discovered everything about this project

[ematipico]

@akkadaya thank you for using Biome!

We have two options that have a very similar name, and we deprecated the one that doesn't follow the naming convention. It will be removed

[nojaf]

Enable .editorconfig support by default

It would be fantastic to have this enabled by default. It's unintuitive that this is set to false, requiring a biome.json file with the following content:

{
  "formatter": {
    "useEditorconfig": true
  }
}

to ensure my .editorconfig file is recognized.

[nhedger]

The v3 extension depends on rootPath, I'll have to check how this impacts the extension. I'll assign this task to myself.

https://github.com/biomejs/biome-vscode/blob/f9aa11226fd6a940f8dcbf0cb2ac951f894983b7/src/session.ts#L266-L269

[ematipico]

The v3 extension depends on rootPath, I'll have to check how this impacts the extension. I'll assign this task to myself.

biomejs/biome-vscode@f9aa112/src/session.ts#L266-L269

We could hold off on the change. The spec marks it as deprecated, but I have no idea if the editors out there are up to date.

[nhedger]

The v3 extension depends on rootPath, I'll have to check how this impacts the extension. I'll assign this task to myself. biomejs/biome-vscode@f9aa112/src/session.ts#L266-L269

We could hold off on the change. The spec marks it as deprecated, but I have no idea if the editors out there are up to date.

As far as I know, VS Code still uses it for their own extensions so I think we could indeed hold for a bit.

[arendjr]

Introduce a JSON formatter option that expands JSON object/array (aka lineWidth: 1)?

I think it's a good idea, but then I'd suggest the JS formatter should support the same option. It would give us another extra option compared to Prettier, but it would be a consistent way of handling this, I feel.

Something like expandLiterals: "always" | "followSource" | "onlyIfExceedingLineWidth", where followSource is our (and Prettier's) current behavior, "always" would be what many people request for JSON files. onlyIfExceedingLineWidth is just something I think makes sense to have as well :)