Add VS Code `extensions.json` file

[hyunbinseo]

If VS Code specific files are going to be added, why not add recommended extensions?

• feat(cli): co-locate css file from usage (+layout.svelte) #780

{
  "recommendations": [
    "bradlc.vscode-tailwindcss",
    "dbaeumer.vscode-eslint",
    "esbenp.prettier-vscode",
    "svelte.svelte-vscode"
  ]
}

The newly added settings.json is part of the VS Code Taliwind CSS extension setup:

{
  "files.associations": {
    "*.css": "tailwind"
  }
}

Personally, I am using Zed and the .vscode directory is just a bloat for me.

[sacrosanctic]

Related:

• feat(cli): co-locate css file from usage (+layout.svelte) #780 (comment)
• vscode does not run eslint on .svelte files #626

Should ide be a prompt?

[jycouet]

That's partly why I was hesitant in adding more of ide specific 😅

Some random thoughts:

• It's an additional question... And that's a bit annoying!
• We can do a tentative of detection... (A bit like the install part)
• if detection didn't work... and there is no addon needing this answer... we should not ask
• It should probaby be multiselect?
• some features are in X but not in Y
• some ide are different but same (eg cursor & vscode & ...) so should it be different or same?
• List of what we recommend is also a topic...

[sacrosanctic]

Or we just cater to VS Code users. It's all in .vscode folder so it's easy to delete for those who don't care to have it.

It's not uncommon in a multi-developer project that contains configs that aren't relevant to them. Vim user with vscode configs. VS Code user with nix configs.

https://survey.stackoverflow.co/2025/technology#most-popular-technologies-dev-envs

[manuel3108]

That's partly why I was hesitant in adding more of ide specific

Totally agree. I do understand the conclusion, but currently I do not agree. The stats presented are barely representative, since they are not focused on web stats. At least, I definitely hope that nobody is using VS (non-code) for web dev. I tried to find similar data in the state of js 2024, but failed.

Let's postpone this and gather more feedback for now.

[sacrosanctic]

Alternatively, we can simply delete the relevant code and defer it to community add-ons. The cat is not out of the bag.