<\/i>Download WebStorm 2018.1 EAP<\/a><\/p>\n To learn more about all the new features added in earlier WebStorm 2018.1 EAP builds, please check out these blog posts<\/a>.<\/p>\n We\u2019ve added a new inspection that checks that the installed version of the node package matches the range specified in package.json.<\/p>\n If the package is listed in WebStorm adds support for a bunch of new TypeScript features: definite assignment assertions<\/a> and numeric separators<\/a> introduced in TypeScript 2.7, and conditional types<\/a> coming in TypeScript 2.8.<\/p>\n WebStorm now supports TypeScript configuration files with names other than tsconfig.json<\/em>.<\/p>\n Applications created with Angular CLI use several TypeScript configuration files located in a different folder: tsconfig.json<\/em>, tsconfig.app.json<\/em>, tsconfig.spec.json<\/em>, and tsconfig.e2e.json<\/em>. WebStorm now recognizes them all as TypeScript config files.<\/p>\n What this means is that the compiler options specified in these files are now correctly applied to the TypeScript files in their scope.<\/p>\n You can add other custom names if you go to Preferences | Editor | File Type<\/em>, search for TypeScript Config<\/em>, and edit the list of associated file names below.<\/p>\n Since TypeScript implements all the standard JavaScript APIs, we\u2019ve decided that it might be helpful to provide links to the corresponding MDN<\/a> articles when showing docs (press F1 to see docs) for standard objects and methods.<\/p>\n If there is no description for a method in the TypeScript lib.d.ts<\/em> file, WebStorm will load the short description from MDN.<\/p>\n We\u2019ve made lots of improvements (and fixed lots of issues) in the way the Implement<\/em> and Override<\/em> actions work in JavaScript and TypeScript. These actions help you implement and override methods and fields inherited from the parent classes and interfaces.<\/p>\n To use Implement<\/em>, put the cursor somewhere in the class or other object and press Ctrl-I<\/em>. For Override<\/em>, press Ctrl-O<\/em>. You can also press Cmd-N\/Alt-Insert<\/em> to open the Generate\u2026<\/em> popup and then select Implement or Override from the list of actions.<\/p>\n The most noticeable change is that Implement Members<\/em> now allows you to add both methods and fields inherited from the parent classes or interfaces. Before, there were two separate actions \u2013 Implement Methods (which has now become Implement Members) and Implement Fields.<\/p>\n Implement now also works not only for classes, but also for other objects. For example:<\/p>\n You can find a full list of issues fixed\u00a0in the WebStorm\u00a0project in the\u00a0Release Notes<\/a>.<\/p>\nCheck installed dependencies<\/h2>\n
devDependencies<\/code> or dependencies<\/code> but is not installed (or is installed but outdated), the quick-fix, available when you press Alt-Enter<\/em>, will suggest running npm install<\/code>.<\/p>\n![\"package-version\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/02\/webstorm-package-version.png\")
<\/p>\n<\/h2>\n
TypeScript improvements<\/h2>\n
Support for new language features<\/h3>\n
Using a different name for tsconfig.json<\/h3>\n
Documentation from MDN<\/h3>\n
![\"doc-from-mdn-in-ts\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/02\/webstorm-doc-from-mdn-in-ts.png\")
<\/h2>\nImplement and Override Members<\/h2>\n
![\"implement-members\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/02\/webstorm-implement-members.png\")
<\/p>\n![\"implement-all\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/02\/webstorm-implement-all.png\")
<\/p>\n