for Windows and Linux
for OS X
In this dialog, activate, deactivate, and configure the behaviour of the built-in TypeScript compiler
In this 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 this area,
specify the version of the compiler to use (RubyMine displays the currently chosen version):
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
typescript package in the current project.
typescript package 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
downloaded from https://github.com/Microsoft/TypeScript/.
Use TypeScript Service
Select this check box
to get native support from the TypeScript Language Service
according to the up-to-date specifications. In this case syntax and error highlighting is performed based on the annotations retrieved from the
TypeScript Language Service while code completion lists contain
both suggestions from the TypeScript Language Service and suggestions calculated by RubyMine itself.
To get only suggestions from RubyMine, click Configure and clear the Code completion check box
in the Service Options dialog box that opens.
By default, the Use TypeScript Service check box is selected.
Enable TypeScript Compiler
Select this check box to activate the built-in 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.
From this 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.
Alternatively, click the Browse button and configure a custom scope in the Scopes dialog box that opens.
For more details on scopes, see
the pages Scopes and
Changed Files: all changed files, that is, all files associated with all existing changelists.
Default: all the files associated with the changelist
Choose this option to
have the built-in compiler analyze the code according to the settings specified in the |
When you open a project, RubyMine starts searching for a
tsconfig.json file in it. If a
tsconfig.json file is found,
the compiler uses the options specified in it. Otherwise an error is reported.
Set options manually
Choose this option to configure the behaviour of the built-in compiler 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
--watch option (Watch input files) is irrelevant.
Select the Generate source maps check box
to generate source maps
otherwise your breakpoints will not be recognised and processed correctly.
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.ts file 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:
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.
the path to the file directory relative to the project root.
the path to the project root folder.
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.
the path to the file relative to the source folder under the content root to the file belongs.
Last modified: 22 March 2017