Skip to content
Bazel support for Visual Studio Code
TypeScript Shell
Branch: master
Clone or download
allevato Merge pull request #143 from thomasvl/simple_options_support
Add settings for startup options and command args.
Latest commit 3ca5f3f Nov 8, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.bazelci Compile fixes/tweaks. May 10, 2019
.vscode Exclude the 'out' and 'node_modules' from the ui. Nov 8, 2019
icons Add an explicit refresh to the Bazel tree view. Dec 17, 2018
media Add logo and some metadata in preparation for publishing. Nov 11, 2018
scripts Add more vendored protos that we plan to use in the future. Dec 11, 2018
src Review feedback. Nov 8, 2019
syntaxes Initial check-in with syntax coloring. Sep 21, 2018
.gitattributes Initial check-in with syntax coloring. Sep 21, 2018
.gitignore Add more vendored protos that we plan to use in the future. Dec 11, 2018
.prettierignore Add tslint and prettier configurations. Dec 5, 2018
.vscodeignore Add a Bazel target tree view to the explorer. Sep 25, 2018
AUTHORS
CHANGELOG.md
CODEOWNERS Add thomasvl@ to CODEOWNERS. May 31, 2019
CONTRIBUTING.md Update the tslint extension to the new/official one. May 10, 2019
CONTRIBUTORS Initial check-in with syntax coloring. Sep 21, 2018
LICENSE Initial commit Aug 28, 2018
README.md Show the badge just for master. Jun 18, 2019
package-lock.json
package.json Review feedback. Nov 8, 2019
tsconfig.json Stub out the Starlark debugger client. Oct 2, 2018
tslint.json Reformat all files and fix lint warnings. Dec 5, 2018

README.md

Bazel plugin for Visual Studio Code

Build Status

This extension provides support for Bazel in Visual Studio.

Features

  • Bazel Build Targets tree displays the build packages/targets in your workspace
  • CodeLens links in BUILD files to directly launch a build or test by simply clicking on the targets
  • Buildifier integration to lint and format your Bazel files (requires that Buildifier be installed)
  • Debug Starlark code in your .bzl files during a build (set breakpoints, step through code, inspect variables, etc.)

Configuring the Extension

This extension adds a Bazel section to the extension settings in Visual Studio Code. If you have Bazel installed in a location that is not on your system path or if you wish to use a different version in the IDE, you should set the Bazel: Executable setting to the location of the Bazel executable.

Similarly, the Bazel: Buildifier Executable setting can be configured if you install Buildifier in a location that is not on your system path.

When Buildifier is installed, the Format Document command in Visual Studio code will reformat BUILD, WORKSPACE, .bzl, and .sky files using the tool and will display lint warnings from those files as you type. By default, this extension does not automatically fix lint warnings during formatting, but you can opt into this by enabling the Bazel: Buildifier Fix on Format setting.

Using the Starlark Debugger

Currently, the Starlark Debugger can be used by right-clicking a build target in the Bazel Build Targets view and selecting "Build Target with Starlark Debugger". This will start the build inside the Visual Studio Code debugger (output will be redirected to the Debug Console pane) and it will pause on any breakpoints hit during execution.

When a Bazel thread is paused, you can step through Starlark code, add watch expressions, and execute arbitrary statements by typing them in the input area of the Debug Console.

Clicking the "Stop" button in the debugger will kill the Bazel process being debugger, allowing you to halt the current build. The Bazel server, however, will continue running.

Contributing

If you would like to contribute to the Bazel Visual Studio extension, please refer to the contribution guidelines for information about our patch acceptance process and setting up your development environment.

You can’t perform that action at this time.