Open Files: all the files that are currently opened in the editor.Ĭurrent File: the file opened in the active editor tab. Scratches and Consoles: all the files from the Scratches and Consoles directory located in the Project tool window. Project Test Files: all the files within the project test source roots. Project Production Files: all the files within the project content roots excluding test sources. Project Files: all the files within the project content roots (see Configuring project structure). ![]() For a project-level File Watcher, you can also click to configure a custom scope in the Scopes dialog that opens. Select one of the predefined scopes from the list. Select the Scope in which the File Watcher is applicable.Ĭhanges in these files will invoke the File Watcher either immediately or upon save or frame deactivation, depending on the status of the Auto-save edited files to trigger the watcher checkbox. File types are recognised based on associations between file types and file extensions.īy default, the field shows the file type in accordance with the chosen predefined template. The File Watcher will consider only files of this type as subject for analyzing and processing. Use the controls in the Files to watch area to define the range of files where you want to apply the File Watcher.įrom the File type list, choose the expected type of input files. By default, WebStorm suggests the name of the selected predefined template.Ĭonfiguring the expected type and location of input files ![]() In the Name field, type the name of the File Watcher. To use a tool that is not on the list, choose Custom. The choice depends on the tool you are going to use. The File Watchers page opens showing a list of File Watchers that are already configured in this project and in the IDE.Ĭlick and choose the predefined template from which you want to create a File Watcher. In the Settings dialog ( Control+Alt+S), click File Watchers under Tools. For more details about plugins, see Managing plugins. Press Control+Alt+S to open the IDE settings and then select Plugins. Make sure the File Watchers plugin is enabled in the settings. Note that using some of these tools in WebStorm requires that you install plugins on the Settings | Plugins page as described in Installing plugins from JetBrains Marketplace. You can still create and enable it manually as described in Creating a File Watcher below.įor information on File Watchers for specific tools, see the corresponding pages: If you click No, WebStorm considers the suggested File Watcher suppressed. When you open a file where a predefined File Watcher is applicable, WebStorm displays a pane where suggests activating it.Ĭlick Yes to activate the File Watcher with the default configuration. A configured File Watcher can be saved in your project settings or in the IDE settings and used in different projects. You can use one of the available templates or configure a File Watcher from scratch. The File Watcher problems inspection is invoked by a running File Watcher and highlights errors specific to it. If the project has no relevant File Watcher configured, WebStorm suggests to add one. The File Watcher available inspection is run in every file where a predefined File Watcher is applicable. You can also configure a custom File Watcher to run any other third-party tool.įile Watchers have two dedicated code inspections: WebStorm provides predefined File Watcher templates for a number of such standard popular third-party tools ( compilers, compressors, prettifiers, and others). To pass any additional parameters to ts-node (for example, -project tsconfig.json), add them in the Application parameters field.īut if I use a non existing path instead of tsconfig.json, I get no complaints that the file does not exist.A File Watcher is a WebStorm system that tracks changes to your files and runs a third-party standalone application. ![]() What am I missing in my configuration?Įdit: I can not only compile the version with require without errors but also execute it without errors. import = require("rxjs/observable/of") īut I'd like to use a scratch file and the import syntax. However, if I try to import some project libraries, e.g. I can run a scratch file without imports using a Node.js run configuration using -require ts-node/register as Node Parameters field (see help). I have a TypeScript project in IntelliJ and like to run a TypeScript scratch file to play with some code and libraries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |