![]() Important! WebStorm EAP builds are not fully tested and might be unstable. ![]() Here are some of the highlights of WebStorm 2018.3 EAP #6 (build 183.3647.15). ![]() For the full list of issues fixed in this update, see the Release Notes. Node.js 10.5 introduced a new experimental feature – worker threads, which can be used for CPU-intensive tasks (check out this blog post for a great overview of the feature). WebStorm now provides code completion for the worker threads API and allows you to debug workers. Debugging workers is available in Node.js 10.12 that was released today. You also need to pass the –experimental-worker flag to the node. When debugging workers in WebStorm, you will see in what thread the breakpoint was hit and you will be able to switch between threads to see the call stack and variables. We have updated the code style options for style sheet languages. First, each language now has its own configuration with a full set of options. Before, most of the options were inherited from the CSS code style and only indents could be configured for each language. Second, we’ve made the use of blank lines in the files more configurable. There are 3 new options located on the Blank lines tab for each language under Preferences | Editor | Code Style | Style Sheets. You can find a full list of addressed issues in the Release Notes.Keep Maximum Blank Lines in Code will remove extra empty lines when you reformat the code (Alt-Cmd-L / ). In the JavaScript files WebStorm will add the actual file extension, and in the TypeScript files, it will always add. You can find the new option in Preferences | Editor | Code Style | JavaScript or TypeScript – Imports tab. This configuration applies to the auto imports and code completion for paths. In the JavaScript and TypeScript code style settings, you can now configure whether the file extension is added to the import path or not. Stay tuned! Code style option for imports: file extension in module name In future updates, we plan to improve the way imports are added and optimized in such projects. This is the first step we are making towards the support of Yarn workspaces. Starting with this update, WebStorm detects projects with Yarn workspaces, and for them, it indexes all the dependencies listed in the package.json files of the workspaces but located in the root node_modules folder. When using Yarn workspaces, the dependencies of all the packages are installed together and are put into the node_modules folder at the root of your project and not next to the package.json file of each workspace.īecause of that approach, WebStorm wasn’t fully indexing the project dependencies and wasn’t able to provide code completion for their APIs. Yarn workspaces help you organize multiple packages into a single repo. There is more about some of the improvements below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |