JSONAISTUDIO
VS Code · IDEbeginner

VS Code settings.json (Team Baseline)

A shared VS Code settings.json enforcing format-on-save, Prettier, consistent tabs and sensible editor defaults across a team.

vscodeidesettingsprettiereslintformatting

Preview

{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.tabSize": 2,
  "editor.insertSpaces": true,
  "editor.rulers": [
    100
  ],
  "files.trimTrailingWhitespace": true,
  "files.insertFinalNewline": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
  },
  "[json]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[typescript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  }
}

AI actions

Documentation

Purpose

Standardise editor behaviour — formatting, whitespace, and save actions — so every developer produces identical diffs.

When to use

Commit as .vscode/settings.json in a repo to give the whole team consistent, opinionated editor defaults.

Required fields

  • No fields are strictly required — every key is optional and overrides a default.

Optional fields

  • editor.formatOnSave — format automatically on save
  • editor.defaultFormatter — which extension formats code
  • editor.tabSize / insertSpaces — indentation
  • "[language]" blocks — per-language overrides

Best practices

  • Commit workspace settings under .vscode/ so they apply to everyone.
  • Set per-language formatters with "[json]", "[typescript]" blocks.
  • Enable codeActionsOnSave for ESLint auto-fix.

Security considerations

  • Never put secrets or tokens in settings.json — it is committed to git.
  • Be cautious enabling settings that auto-run tasks or code on folder open.