Quantcast
Channel: Active questions tagged visual-studio-code - Stack Overflow
Viewing all articles
Browse latest Browse all 99142

Is it possible to install and enable workspace extensions in vscode with the .vscode folder?

$
0
0

What I want to achieve:

  1. I want my projects to be self-contained in a manner that will allow collaborators to start working on them with all the proper linting and language features etc.. (I know this is a bit harsh in the sense that i am "forcing" an IDE in it, but for the sake of the problem it is helpful.)

  2. I want my projects to be self-contained so that i have full config control over which extensions work and which don't when i approach working on them. I don't want to be depenedant on my own machine with my own vscode user config. I don't want to be dependent on extension I have installed in the past. And i also don't want different extension to be mixed up. I want everything disabled on the global user space and only enabled in controlled manned via some in project setting file.

What I think I basically need:

A VSCode extension manager that can work locally in the dir. Sort of like an npm for vscode.

So i would be able to structure extension "dependencies" and run an install and locally enable the extension to work on the specific workspace.

extension.package

{
  "extensions": {
    "eslint": "6.4^""babel": "15.2^"
  }
}

Then there would be the regular configuration files for these extension available already with the git - and if not perhaps they can be auto-generated with some default settings.

and all the developer would need to do is run some bash code command.


Does something like this exist? Is such a functionality available to achieve?


Viewing all articles
Browse latest Browse all 99142

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>