commit | cd1a88fa383527d0df761b5026ec33c941d48691 | [log] [tgz] |
---|---|---|
author | Solly Ross <sollyross@google.com> | Fri May 13 16:11:12 2022 -0700 |
committer | Solly Ross <sollyross@google.com> | Mon May 23 12:50:09 2022 -0700 |
tree | 94b5b76d2c4e31560ded161d638c92ea9f119dae | |
parent | 57bad0f989b329cc4c43cb42f224d4347444fd9d [diff] |
Include THIRD_PARTY_NOTICES.txt This includes a THIRD_PARTY_NOTICES.txt with copyright coverage for each of the third-party components included in the release, with pointers to the relevant license files (which are included in the final copy of the package). Fixed: 97476 Change-Id: Ie61dc675b8de3b6fc9c5328c3c7e303deb378213
The Fuchsia VS Code extension integrates the commonly needed tasks for Fuchsia development into VS Code.
This is a Work In Progress Currently supporting:
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:
npm install vsce
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:
git clean -xdf
[^3] (WARNING: this will delete everything not tracked by git)npm ci
[^1]npm test
npx vsce package
[^2]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@
[^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