![]() ![]() src/** - Stubbed code for the extension. ![]() This will show in the ‘Details’ section in the extension gallery. README.MD - The description of your extension.This will show in the ‘Changelog’ section in the extension gallery. ![]() CHANGELOG.MD - The change logs for the extension.tslint.json - The TypeScript linting rules.tsconfig.json - The config file for the TypeScript compiler.package.json - Describes the extension and where to find its entry point and activation trigger.These are the key files in the project template: The Yeoman generator will produce a ‘duck-generator’ project with the following structure: /duck-generator /src /test - index.ts - extension.ts - package.json - tsconfig.json - tslint.json - CHANGELOG.MD - README.MD - vsc-extension-quickstart.md Select the, “New Extension (TypeScript),” option. Open a terminal at your project folder and run yo code to start the generator for the extension. We will use Yeoman to create a project template for developing the extension using Microsoft’s preferred structure and settings. Nodejs LTS (8.11.x, currently) and NPM 5.xįrom the terminal, install Yeoman and the Visual Studio Code Extension generator.You will need to have the following tools installed to create an extension for VS Code: * A typical duck structure from re-ducks */ /state /ducks /quack - actions.js - index.js - operations.js - reducers.js - selectors.js // Optional, still generated - test.js - types.js - utils.js // Not generated Setup ![]() The term ‘ducks’ refers to the folder and files that you have to create for managing redux state using the re-ducks pattern.Įvery duck needs to have six to eight files in it, and in Visual Studio Code (VS Code), it’s painful to manually create them every single time you add a new duck to your project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |