Prep for switching CI to container runners

CI is moving to containers, but needs a workaround due to how it checks
out git directories.  Ideally this'll be fixed by CI long-term, but in
the short term this is the workaround.

This also switches to python 3.9, since 3.6 isn't available in the
default container images.

Finally, we'd have to update npm to v9 since v8 gets... clever with
detecting running as root and then trying to run as something else
instead (by checking the current directory owner, which is non-root due
to the same reasons as the above checkout).  However, npm@9 is not
compatible with our current Node version (17.9.0), so just update to the
latest node version (19.4.0), which comes with npm@9 ootb.

This last bit prompted updating a few packages to be compatible with
Node 19 (including removing oniguruma, which is actually deprecated &
archived -- see https://fxbug.dev/119360)

Change-Id: Ib0e407cdadaae9301ad41d9319a1e42a9d08e790
Reviewed-on: https://fuchsia-review.googlesource.com/c/vscode-plugins/+/788446
Reviewed-by: Brian Bosak <bbosak@google.com>
Reviewed-by: Clayton Wilkinson <wilkinsonclay@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
9 files changed
tree: 8f0090e73e34de902614014c8e5d45890d398870
  1. .ci/
  2. .kokoro/
  3. .vscode/
  4. docs/
  5. media/
  6. resources/
  7. src/
  8. syntax/
  9. testdata/
  10. webviews/
  11. .eslintrc.json
  12. .gitignore
  13. .vscodeignore
  14. AUTHORS
  15. build-helpers.mjs
  16. build.mjs
  17. BUILDING.md
  18. CHANGELOG.md
  19. CONTRIBUTING.md
  20. LICENSE
  21. OWNERS
  22. package-lock.json
  23. package.json
  24. PATENTS
  25. README.md
  26. THIRD_PARTY_NOTICES.txt
  27. TROUBLESHOOTING_ZXDB.md
  28. tsconfig.json
  29. web-test-runner.config.mjs
README.md

Fuchsia extension for VS Code

This VS Code extension implements the commonly needed functionality for Fuchsia development.

This is a Work In Progress Currently supporting:

  • Interacting with the fuchsia target device.
    • Setting the default target.
    • Sending commands to the target.
  • Debugging C/C++ components.
  • Filtering and listening to target logs.
  • FIDL syntax highlighting

FFX path settings

The FFX tool path can be set under Settings > Extensions > Fuchsia SDK. If this path is not set, the extension will automatically search for it at:

  • ./tools/ffx
  • ./.jiri_root/bin/ffx

Recommended extensions

Contributing

Issues/feedback

  • Please report issues/feedback here.

Legal Notice

Use of the Fuchsia core developer tools is subject to the Google Terms of Service. The Google Privacy Policy describes how data is handled in your use of this service.