chore: remove .editorconfig file

[bjohansebas]

Using this file was proposed in #3221 and added in efd7032, which made sense at the time because Standard was not yet integrated into the repository and organization. Now that we have Standard (which will likely change soon, see expressjs/discussions#327).

This is just another configuration file and, in my opinion, it doesn't make sense to relate it to the discussion of the new linter that will be chosen, since they serve different purposes, in my opinion.

In any case, if you don't have an extension in VSCode or your editor that supports this file, it won't work.

related: expressjs/body-parser#601

[Phillip9587]

I am against removing it. Having this file ensures consistent practices for things like indentation, line endings, and spacing across Editors and IDEs. It can also help reduce unnecessary merge conflicts and make collaboration smoother overall. It’s a small addition that can make a big difference.

Let's discuss it in expressjs/discussions#327

[sheplu]

In any case, if you don't have an extension in VSCode or your editor that supports this file, it won't work.

I may be wrong but editorconfig is understood by default by all major IDE, vscode does not need a plugin for that and I am fairly certain that this is the same for other IDEs

On a personal view, I still enforce using that to have the right per default config on for all IDEs - so I would mostly be "against removing it"

[bjohansebas]

vscode does not need a plugin for that and I am fairly certain that this is the same for other IDEs

In these editors, a plugin needs to be installed https://editorconfig.org/#download

[Phillip9587]

Yes, some editors do require a plugin. But take a look at the list of editors that support it natively: https://editorconfig.org/#pre-installed

It makes a lot of sense to keep that file - and maybe even add it to all our other repos.

[ctcpip]

we should keep .editorconfig in all repos (and add them if they are missing)

[sheplu]

I would agree to have then in all repositories, and in sync with the expected linting configuration. We should also define the content to harmonize it.