HomeWorkBlogCiphera
/ blog/vscode-setup-nextjs-go
blog / vscode-setup-nextjs-go / overview.md

My Custom VS Code Setup for Next.js and Go

The exact extensions, settings, and linters I use to maintain productivity across strict Go backend microservices and fluid Next.js frontend code.

Switching contexts between Go and TypeScript can be jarring. Here is how I configure VS Code to handle both seamlessly.

Extensions:

  1. Go (Official)
  2. ESLint & Prettier
  3. Tailwind CSS IntelliSense
  4. Error Lens: Inlines errors next to the code.

Settings.json Magic:

{
  "editor.formatOnSave": true,
  "[go]": {
    "editor.defaultFormatter": "golang.go",
    "editor.codeActionsOnSave": {
      "source.organizeImports": true
    }
  },
  "[typescriptreact]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  }
}

This ensures gofmt runs for Go, and Prettier runs for React, without them fighting each other.

Tags

build-in-publicworkflow

Related Blogs

build-in-public

Why I Built My Own CMS Instead of Using Contentful or Sanity

Headless CMS platforms are powerful, but they abstract away the database, limit your architecture, and introduce vendor lock-in. Here is a build-in-public look at why writing a bespoke CMS on Supabase was the best engineering decision I made.

build-in-public

Burnout and Scope Creep: Lessons from VulnHunter

How adding 'just one more feature' almost killed a 6-month side project.

0
0