The File Watcher wakes up and launches the transpiler as soon as your project is saved manually ( File | Save All or Ctrl+S) or automatically. Change the action that triggers the File Watcher with source maps that let you step through your app during a debugging session.Īlthough the default settings are sufficient to run the compiler successfully, let's still take a closer look at them to see how the File Watcher's behavior can be customized. As a result, two files are generated and shown nested under Page.scss: This triggers our File Watcher and the compiler processes Page.scss. Let's change grid.scss, for example, replace margin-left: 0 at line 31 with margin-left: 12px. In the New File Watcher dialog, that opens, all the mandatory fields are already filled in.Īctually, these settings are sufficient to run the compiler successfully. The example below shows how Page.scss is compiled into CSS when you save your project manually or automatically and how the changes to _grid.scss are reflected in the generated CSS file.Ĭreate a File Watcher of the type SCSS: open the Settings/Preferences dialog ( Ctrl+Alt+S), go to Tools | File Watchers, click on the toolbar, and select SCSS from the list. Suppose your project is structured as follows:Īs you can see, _grid.scss is imported in Page.scss. Otherwise, type the path manually or click and choose the file location in the dialog that opens. If you followed the standard installation procedure with npm, WebStorm locates the required files itself and fills in the field automatically. In the Program field, specify the path to the compiler archive depending on the chosen predefined template. Depending on the tool you are going to use, choose the Less, Sass, or SCSS predefined template from the list. The File Watchers page that opens shows the list of already configured File Watchers.Ĭlick or press Alt+Insert. In the Settings/Preferences dialog ( Ctrl+Alt+S), click File Watchers under Tools. However, in the Project Tree, they are shown under the source file which is now displayed as a node. The location of the generated files is defined in the Output paths to refresh field of the New Watcher dialog. The file has the name of the source Sass, Less, or SCSS file and the extension. WebStorm creates a separate file with the generated output. If the Auto-save edited files to trigger the watcher checkbox is cleared, the File Watcher is started upon save ( File | Save All, Ctrl+S) or when you move focus from WebStorm (upon frame deactivation). If the Auto-save edited files to trigger the watcher checkbox is selected, the File Watcher is invoked as soon as any changes are made to the source code. If an applicable File Watcher is configured and enabled in the current project, WebStorm starts the compiler automatically upon the event specified in the New Watcher dialog. If such File Watcher is configured but disabled, WebStorm displays a popup that informs you about the configured File Watcher and suggests to enable it. When you open a file, WebStorm checks whether an applicable File Watcher is available in the current project. To compile your code automatically, you need to configure a Sass, Less, or SCSS File Watcher which will track changes to your files and run the compiler. Learn more from the Less official website. Learn more from the Sass official website. In the embedded Terminal ( Alt+F12), type: Make sure the File Watchers and Less or Sass required plugins are enabled on the Settings/Preferences | Plugins page, tab Installed, see Managing plugins for details. Make sure you have Node.js on your computer. You can also use the compiler from the command line or configure it as a third-party tool, see Configuring Third-Party Tools for details. To use a compiler in WebStorm, you need to configure it as a File Watcher based on the relevant predefined template. WebStorm integrates with compilers that translate Sass, Less, and SCSS code into CSS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |