Go to file
Michael Borisov bc6333bd20 fix root dir resolution for WSL2 2023-04-10 21:43:43 +02:00
.github chore: cleanup 2022-12-25 00:49:04 +01:00
.vscode chore: cleanup 2022-12-25 00:49:04 +01:00
images chore: cleanup 2022-12-25 00:49:04 +01:00
src fix root dir resolution for WSL2 2023-04-10 21:43:43 +02:00
tests chore: cleanup 2022-12-25 00:49:04 +01:00
.eslintrc.js chore: cleanup 2022-12-25 00:49:04 +01:00
.gitattributes Initial commit 2021-01-15 11:50:07 +00:00
.gitignore feat: dotnet (windows only) template 2021-01-25 20:35:48 +00:00
.prettierrc chore: cleanup 2022-12-25 00:49:04 +01:00
.vscodeignore Initial commit 2021-01-15 11:50:07 +00:00
CHANGELOG.md fix root dir resolution for WSL2 2023-04-10 21:43:43 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md 2023-04-04 20:04:04 +02:00
LICENSE other: change the license to BSD 2021-04-26 17:13:56 +00:00
README.md chore: update the docs 2022-09-11 12:54:35 +00:00
environment.yml feat: make environment available for all extensions 2022-12-23 11:25:15 +01:00
jest.config.js chore: cleanup 2022-12-25 00:49:04 +01:00
package-lock.json 0.1.14 2023-04-04 20:31:22 +02:00
package.json 0.1.14 2023-04-04 20:31:22 +02:00
tsconfig.json chore: cleanup 2022-12-25 00:49:04 +01:00

README.md

vscode-micromamba

Build Status Coverage Status Visual Studio Marketplace


Content


The Aim

Provide a convenient way to install developer tools in VSCode workspaces from conda-forge with micromamba. Get NodeJS, Go, Rust, Python or JupyterLab installed by running a single command.

Inspired by Robocorp RPA developer tools:

  • RCC - a command-line tool to run software robots and integrate with the Robocorp Cloud
  • Robocorp Lab - a JupyterLab based IDE to build software robots
  • Robocorp Code - a VSCode extension to build software robots

Commands

Micromamba: create environment

This command creates a file - environment.yml describing configuration. The environment.yml is a mamba environment file The extension comes with a number of templates but you could change it to your needs and re-run init command.

  1. Open command palette (Ctrl+Shift+P)
  2. Type - micromamba create environment
  3. Choose a template from a list
  4. See the micromamba execution progress in terminal
  5. The environment is activated automatically

Micromamba: deactivate environment

  1. Open command palette (Ctrl+Shift+P)
  2. Type - micromamba deactivate environment
  3. See the micromamba execution progress in terminal

Micromamba: activate environment

  1. Open command palette (Ctrl+Shift+P)
  2. Type - micromamba activate environment
  3. Choose an environment from a list of created environments
  4. See the micromamba execution progress in terminal

Micromamba: remove environment

  1. Open command palette (Ctrl+Shift+P)
  2. Type - micromamba remove environment
  3. Choose an environment from a list of created environments
  4. See the micromamba execution progress in terminal

Micromamba: clear all

Clear all command removes micromamba, packages, and reset environment to the initial state.

  1. Open command palette (Ctrl+Shift+P)
  2. Type - micromamba clear all
  3. See the micromamba execution progress in terminal

DotEnv file support

DotEnv file is a convenient way to provide environment variables to other extensions or user scripts. Each time user creates or activates an environment there is a ~/.micromamba/.env.{prefix-name} file created.

Multi-root workspaces

With multi-root workspaces all operations will work the same way as if you open the first workspace folder in VSCode. The idea is that the first workspace folder is a target folder.

Let's say you have a project.code-workspace with content:

{
  "folders": [
    {
      "path": "folderA"
    },
    {
      "path": "folderB"
    }
  ]
}

Assuming folders are already created, when you open the workspace in VSCode and command to create a micromamba environment, you'll see the following directory structure:

.
├── folderA
│   ├── .micromamba
│   └── environment.yml
├── folderB

How to get it?

Simply open Micromamba - Visual Studio Marketplace and click "Install". Alternatively open Visual Studio Code, go to the extension view and search for "Micromamba".

For detailed releases and migration help, please see releases.

Maintainers

Michael Borisov (@corker).

Want to Contribute?

Thanks for considering! Check here for useful tips and guidelines.

License

We use a shared copyright model that enables all contributors to maintain the copyright on their contributions.

This software is licensed under the BSD-3-Clause license. See the LICENSE file for details.