On this page:
- Configuring and activating the built-in TypeScript compiler
- Transpiling TypeScript using the built-in compiler
- Running the built-in TypeScript compiler as a before-launch task
Configuring and activating the built-in TypeScript compiler
- Open the Settings / Preferences Dialog by pressing Ctrl+Alt+S or by choosing for Windows and Linux or for OS X, and click Typescript under Languages & Frameworks.
- On the TypeScript Compiler page that opens, select the Enable TypeScript Compiler check box to activate the compiler. When the check box is selected, syntax highlighting and code completion are provided based only on the data from the built-in Typescript compiler. After you select this check box, the fields below in the area become active and you can configure the behaviour of the compiler. By default, the check box is cleared.
To have the compiler "wake up" upon any change to a TypeScript file, select the Track changes check box.
When this check box is cleared, the built-in compiler ignores changes to TypeScript files. To re-activate the compiler, open the TypeScript Compiler Tool Window (), and click the Compile All button on the toolbar.
In the other fields of the TypeScript Compiler page, specify the following:
- In the Node interpreter field, specify the location of the Node.js executable file. In most cases, RubyMine detects the Node.js executable and fills in the field automatically.
In the TypeScript version area,
specify the version of the compiler to use (RubyMine displays the currently chosen version):
- Click Edit.
In the Configure TypeScript Compiler dialog box that opens, choose one of the following options:
Detect: if you choose this option, RubyMine searches for a
typescriptpackage in the current project. If a
typescriptpackage is found, RubyMine uses it. Otherwise the default bundled package is used. This option is chosen by default.
Bundled: if you choose this option, RubyMine uses it without attempting to find another
Custom directory: choose this option to use a custom version of the compiler.
In the text box, specify the location of the
lib.es6.d.tsfiles downloaded from https://github.com/Microsoft/TypeScript/.
- Detect: if you choose this option, RubyMine searches for a
From the Scope drop-down list, choose the scope to apply the compiler in.
The available options are:
- Project Files: all the files within the project content roots (see Content Root and Configuring Content Roots).
- Project Production Files: all the files within the project content roots excluding test sources.
- Project Test Files: all the files within the project test source roots.
- Open Files: all the files that are currently opened in the editor.
VCS Scopes: these scopes are only available if your project is under version control.
- Changed Files: all changed files, that is, all files associated with all existing changelists.
Default: all the files associated with the changelist
Choose the Set options manually to configure transpilation manually:
In Command line options field,
specify the command line options to be passed to the compiler.
See the list of acceptable options at TSC arguments.
Note that, the
--watchoption (Watch input files) is irrelevant.
Select the Compile main file only check box
to have RubyMine compile only a specific file and the files that are referenced from it and ignore all the other files in the project.
This may be helpful if you have a dedicated
main.tsfile which only references other files.
Select the Use output path check box
Specify the path to this folder explicitly or use one of the listed available macros in the format:
$<macros_name>$. The available macros are:
FileDir: the path to the folder where the file is stored.
FileRelativeDir: the path to the file directory relative to the project root.
FileDirRelativeToProjectRoot: the path to the file directory relative to the project root.
ModuleFileDir: the path to the project root folder.
SourcePath: the path to the source folder under the content root to which the file belongs, see Configuring Content Roots and Configuring Folders Within a Content Root.
FileDirRelativeToSourcePath: the path to the file relative to the source folder under the content root to the file belongs.
- In Command line options field, specify the command line options to be passed to the compiler. See the list of acceptable options at TSC arguments. Note that, the
Choose the Use tsconfig.json option,
have the built-in compiler analyze the code according to the settings specified in the
tsconfig.jsonfile. When you open a project, RubyMine starts searching for a
tsconfig.jsonfile in it. If a
tsconfig.jsonfile is found, the compiler uses the options specified in it. Otherwise an error is reported.
Transpiling TypeScript using the built-in compiler
To activate a previously configured built-in transpiler, select the Enable TypeScript Compiler check box
on the TypeScript Compiler page.
Alternatively, use the buttons on the pane which RubyMine displays when you open a TypeScript file.
- To enable an already configured compiler, click Enable.
- To configure a compiler, click Configure and specify the settings on the TypeScript Compiler page that opens.
- To leave the compiler disabled and suppress showing the pane in the future, click Dismiss, whereupon the compiler can be later activated only on the TypeScript Compiler page.
View the errors detected during compilation, compile separate files and the entire project in the TypeScript Compiler Tool Window.
If you have configured the compiler to track changes, which is the default behaviour, the tool window opens automatically
as soon as you start editing a TypeScript file.
- Click the Compile Current File toolbar button to run the compiler against the entire file opened in the active editor tab. This approach is helpful if you do not want the compiler to wake up on any change as you edit your code and for this purpose the Track Changes check box on the TypeScript page of the Settings dialog box is cleared.
- Click the Compile All toolbar button to run the compiler against all the TypeScript files in the current project. If you click this button from the Current Errors pane, after compilation RubyMine switches to the Project Errors pane.
- To clear the contents of the current pane, click the Clear All toolbar button .
- To navigate to the fragment of code where an error occurred during compilation, select the error message in question and choose Jump to Source on the context menu of the selection.
the source map file has the name of the source TypeScript file and the
In the Project Tree, the files are shown under the source TypeScript file
which is now displayed as a node.
This presentation is preserved even if you turn off the compiler during a RubyMine session.
Running the built-in TypeScript compiler as a before-launch task
- Open the Run/Debug Configurations dialog by choosing on the main menu, and select the required configuration from the list or create it anew by clicking and choosing the relevant run configuration type.
- In the dialog box that opens, click in the Before launch area and choose Compile TypeScript from the drop-down list.
- In the TypeScript Compile Settings dialog that opens, select or clear the Check errors check box to configure the behaviour of the compiler in case any errors are detected: