Google Git
Sign in
fuchsia / vscode-plugins / e6bef41c7af48a1704e7e143423fbe06dd37927c
commite6bef41c7af48a1704e7e143423fbe06dd37927c[log] [tgz]
authorMiguel Flores Ruiz de Eguino <miguelfrde@google.com>Fri May 20 17:01:56 2022 +0000
committerMiguel Flores Ruiz de Eguino <miguelfrde@google.com>Fri May 20 19:33:10 2022 +0000
treece27c45fb8da8cce62ae564b4eba1441307ee5e2
parent76e0c7a3ac8b78ebbdf0db3be7ccd0ada4963bc2 [diff]
[logging] Send ffx log stderr to the output channel

Change-Id: I31375e13b3066dccb89114b2f6bfa5b76ebe7adf
4 files changed
tree: ce27c45fb8da8cce62ae564b4eba1441307ee5e2
  1. .vscode/
  2. media/
  3. resources/
  4. src/
  5. webviews/
  6. .eslintrc.json
  7. .gitignore
  8. .vscodeignore
  9. AUTHORS
  10. CONTRIBUTING.md
  11. LICENSE
  12. OWNERS
  13. package-lock.json
  14. package.json
  15. PATENTS
  16. README.md
  17. tsconfig.base.json
  18. tsconfig.json
  19. tsconfig.test.json
  20. tsconfig.webviews.json
  21. webpack.config.js
README.md

Fuchsia extension for VS Code

What does it do?

The Fuchsia VS Code extension integrates the commonly needed tasks for Fuchsia development into VS Code.

This is a Work In Progress Currently supporting:

  • Commands for:
    • Saying Hello
    • Submitting Feedback to the issue tracker
  • A Fuchsia View container
    • List of Fuchsia targets.
  • Configuration parameters

Getting started

VS Code extension development requires Node.js. Our development workflow has been tested with 1.17.9, but newer versions should work. Older versions may break.

You can install a recent copy of Node by any of the following

a. Downloading Node from its website and placing it on your PATH b. Downloading Node via nvm c. Downloading Node from CIPD and placing it on your PATH

Read about extensions, concepts and guides: https://code.visualstudio.com/api/get-started/extension-anatomy.

To run the extension:

  • Open this directory in VS Code
  • Open the terminal window and run npm install vsce
  • Click “Run”. This will open another instance with the extension installed.

Settings

FFX path

The FFX path can be set under Settings > Extensions > Fuchsia SDK. If a path is not set, the extension will automatically search and set it if it can find it at:

  • tools/ffx
  • .jiri_root/bin/ffx

Packaging the extension

  • cd to vscode-plugins (This directory).
  • git clean -xdf [^3] (WARNING: this will delete everything not tracked by git)
  • npm ci [^1]
  • npm test
  • npx vsce package [^2]

Sharing internal to Google

Note: We‘re working on build and publish workflow that complies with Google’s internal practices. It is coming soon to the extension marketplace.

In the meantime, Googlers building the extension, please copy it to

$ cp vscode-fuchsia-0.0.2.vsix /google/data/rw/teams/tq-devrel/vscode-extensions/

Questions? Let us know: fuchsia-editor-team@

Related extensions

  • clangd for C++ development.
  • bazel for the Bazel build system.

[^1]: npm ci is like npm install, except that it re-downloads a clean copy of the node_modules directory using package-lock.json and errors out if package-lock.json ii out of sync with package.json

[^2]: npx runs commands from npm packages without having to globally install them

[^3]: this cleans out any files that are not tracked by git, to ensure we have a clean build, in case we missed anything in our .vscodeignore