Add .vscode/settings.json & extensions.json files to project

[coliff]

On all projects I work on with others I always commit a .vscode folder with extensions.json and settings.json files so that when a colleague or outside contributor clones the repo they will be recommended to install helpful extensions and have their code automatically fixed/linted thanks to the settings.json config.

As VS Code has such a huge marketshare (and it's close competitors are forks of VS Code and support the same files) it could make sense to add it to the project and may mean that the code quality of contributed PRs may improve as bugs, spelling mistakes and linting issues are fixed earlier.

A couple of suggested configs below, I'm sure they could be improved upon though such as adding default formatters for more file-types.

{
  "recommendations": [
    "dbaeumer.vscode-eslint",
    "EditorConfig.EditorConfig",
    "streetsidesoftware.code-spell-checker",
    "stylelint.vscode-stylelint"
  ]
}

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit",
    "source.fixAll.stylelint": "always"
  },
  "editor.renderWhitespace": "all",
  "scss.validate": false,
  "stylelint.enable": true,
  "stylelint.validate": ["scss"]
}

If you don't want to do this, it's fine, just a suggestion :-)

[julien-deramond]

I'm personally not opposed to the idea. Like you said, it's quite common when contributing to other Open Source projects. We could even include a launch.json launching the docs server. I'm definitely interested in trying out the configuration you suggested, using either VS Code or Cursor, to see how it works in practice.

If you don’t mind, would you be able to open a PR so we can experiment with it?

@mdo Would you also be open to adding this to the repo?