Open the Codewind view in the Explorer view group or enter Focus on Codewind View into the Command Palette. If you do not see the Codewind view in either the Explorer view or the Command Palette, the extension did not install correctly.
Codewind requires the installation of additional Docker images to run. Choose Install when prompted to complete the installation. The installation may take a few minutes to complete. Codewind creates a folder called codewind-workspace within your home directory to contain your projects. On Windows, this is the C:\codewind-workspace directory. When the installation is complete, you can open the codewind-workspace folder or a project within the workspace as your VS Code workspace. The tools offer to open the workspace for you if it’s not open already.
From a terminal, run export CW_TAG=latest (or your Windows equivalent).
Close all instances of VS Code.
Launch VS Code (code) from the same shell so the environment is picked up.
You can also build the extension .vsix yourself by running vsce package from dev/. Refer to the Jenkinsfile to see the exact steps the build runs.
The extension bundles dependency executables. These are gitignored, but should be kept up-to-date on your local system with the same versions used in the Jenkinsfileparameters section. Run dev/bin/pull.sh to download the dependencies. Also see dev/bin/README.txt.
The prebuild script is used in the CI builds to build separate versions of the extension for VS Code and Theia, since each of those has some commands that the other does not. It deletes inapplicable commands from the package.json, and does not modify any ts/js code. Run this before vsce package to get a closer-to-production build, but be ready to revert the changes.