WebStorm 6.0.1 Web Help

CoffeeScript code is not processed by browsers that work with JavaScript code. Therefore to be executed, CoffeeScript code has to be translated into JavaScript. This operation is referred to as transpilation and the tools that perform it are called transpilers.

WebStorm supports integration with the coffee-script and coffee-script-redux tools. The coffee-script transpiler translates CoffeeScript code into JavaScript. The coffee-script-redux transpiler creates source maps that set correspondence between lines in your CoffeeScript code and in the generated JavaScript code, otherwise your breakpoints will not be recognised and processed correctly. So if you want only to run your application, it is enough to apply the coffee-script transpiler while to enable debugging it you will need to run both tools.

In WebStorm, transpiler configurations are called File Watchers. For each supported transpiler, WebStorm provides a predefined File Watcher template. Predefined File Watcher templates are available at the WebStorm level. To run a transpiler against your project files, you need to create a project-specific File Watcher based on the relevant template, at least, specify the path to the transpiler to use on your machine.

On this page:

Installing and configuring a CoffeeScript transpiler
  1. Download and install the Node.js framework. The CoffeeScript transpiler is started through Node.js and the Node Package Manager (npm) is also the easiest way to download the transpiler. For details on using Node.js in WebStorm, see the section Node.Js

    Tip

    Alternatively, you can define Node.js as an external tool, as described in the section Configuring third-party tools. This approach is helpful, when you need facilities that are missing in the plugin, for example, the possibility to pass certain parameters as wildcards.

  2. Make sure the Node.js plugin is enabled. The plugin is bundled with WebStorm and activated by default. If it is not, enable the plugin.
  3. Make sure the File Watchers plugin is enabled. The plugin is bundled with WebStorm and activated by default. If it is not, enable the plugin.
  4. Download and install the CoffeeScript transpiler. The easiest way is to use the Node Package Manager (npm), which is a part of Node.js.
    1. Switch to the directory where the Node Package Manager (npm) is stored or define a path variable for it so it is available from any folder.
    2. Do one of the following depending on your further plans:
      • To run the generated JavaScript code, download the coffee-script through the following command at the command line prompt:
        npm install coffee-script
                                        
      • To debug your code, you will need source maps that set correspondence between lines in your CoffeeScript code and the generated JavaScript code, otherwise your breakpoints will not be recognised and processed correctly. Source maps are generated by the coffee-script-redux transpiling tool. Type the following command at the command line prompt:
        npm install coffee-script-redux
                                        

      In either case, the tool is installed under Node.js so Node.js, which is required for starting the tool, will be specified in the path to it.

      Tip

      The executable files of both transpilers have the same name coffee.cmd (though luckily differ in contents). Therefore to have both tools available, you need to rename the executable of the one that was downloaded first or move it to another folder under Node.js.

      For more information about installing CoffeeScript transpilers, see https://npmjs.org/package/coffee-script and https://npmjs.org/package/coffee-script-redux.

Creating a File Watcher

WebStorm provides a common procedure and user interface for creating File Watchers of all types. The only difference is in the predefined templates you choose in each case.

  1. To start creating a File Watcher, open the Project Settings and click File Watchers. The File Watchers page that opens, shows the list of File Watchers that are already configured in the project.
  2. Click the Add button new.png or press Alt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+Insert or Ctrl+NAlt+InsertControl N or Control EnterControl N or Control EnterMeta N or Control Enter and choose the predefined template from the pop-up list.
    • If you are going to run your CoffeeScript without debugging, choose CoffeeScript. Your code will be just translated to JavaScript.
    • If you are going to debug your code, choose CoffeeScript Source Map. As a result, the source maps will be created.
  3. In the Program text box, specify the path to the coffee.cmd file. Type the path manually or click the Browse button browseButton.png and choose the file location in the dialog box that opens.
  4. Proceed as described on page Using File Watchers.

Transpiling the CoffeeScript code

When you open a CoffeeScript file, WebStorm checks whether an applicable file watcher is available in the current project. If such file watcher is configured but disabled, WebStorm displays a pop-up window that informs you about the configured file watcher and suggests to enable it.

If an applicable file watcher is configured and enabled in the current project, WebStorm starts it automatically upon the event specified in the New Watcher dialog.

  • If the Immediate file synchronization check box is selected, the File Watcher is invoked as soon as any changes are made to the source code.
  • If the Immediate file synchronization check box is cleared, the File Watcher is started upon save (File | Save All, Shortcut Missing) or when you move focus from WebStorm (upon frame deactivation).

The transpiler stores the generated output in a separate file. The file has the name of the source CoffeeScript file and the extension js or js.map depending on the transpiler type. The location of the generated files is defined in the Output Paths text box of the New Watcher dialog. Based on this setting, WebStorm detects transpiler output. However, in the Project Tree, they are shown under the source .coffee file which is now displayed as a node.

Previewing the transpilation results without running a transpiler

WebStorm can perform static analyses of your CoffeeScript code without actually running a transpiler and display the predicted transpilation output in the dedicated read-only viewer.

  1. Open the desired CoffeeScript file in the editor, and right-click the editor background.
  2. On the context menu, choose Preview Compiled CoffeeScript File. The preview is opened in the dedicated read-only viewer: the left-hand pane shows the original CoffeeScript source code and the right-hand pane shows the JavaScript code that will be generated by the transpiler when it runs.

See Also

Procedures:

Language and Framework-Specific Guidelines:

Reference:

External Links:

Web Resources: