beachy13 / azure-devops-extension-yeoman-generator

Generates a basic Azure DevOps extension with support for hot reload and debugging in VS Code

Azure DevOps extension generator

Generates a basic Azure DevOps extension with support for hot reload and debugging in VS Code. For more information about how hot reload and debugging works with Azure DevOps extensions, please see the azure-devops-extension-hot-reload-and-debug repo, as well as the accompanying blog post.

Installation

First, install Yeoman and generator-azure-devops-extension using npm (we assume you have pre-installed Node.js).

npm install -g yo
npm install -g @microsoft/generator-azure-devops-extension

Then generate your new project:

yo @microsoft/azure-devops-extension

Output

Running the generator will result in the following file structure:

.
├── .eslintrc.js
├── .gitignore
├── .vscode
│   └── launch.json
├── README.md
├── configs
│   ├── dev.json
│   └── release.json
├── img
│   └── world.png
├── package.json
├── src
│   └── hub
│       ├── hub.html
│       ├── hub.scss
│       └── hub.tsx
├── tsconfig.json
├── vss-extension.json
└── webpack.config.js

What's next?

Now that you have generated a new project, you are ready to start debugging. Refer to the generated readme in your new project for instructions on how to get started. You should also check out our azure-devops-extension-hot-reload-and-debug repo for an in-depth look at how these features work.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.