![]() ![]() In WebStorm 2017.3 we’ve experimented with using separate lexers for every JavaScript language level (e.g. The lexer splits input files into a stream of tokens and it is used for many IDE subsystems, including indexing and syntax highlighting. Quite often in the CPU snapshots that our users send to us we see that the indexing is affected by the performance of the lexer. Right now it’s done only for the standard JavaScript APIs that we’ve mentioned above, but we plan to extend it further in the future. We’ve introduced pre-built indices: this allowed us to ship some index information right with the IDE distribution.This gives us a small decrease to the indexed file size. We’ve switched from using the custom definition files for the standard JavaScript and DOM APIs to using the TypeScript type declarations files.For the projects generated with Angular CLI, it allowed us to cut about 2MB of files from indexing. The biggest one was the switch from indexing the compiled JavaScript files to using the metadata.json files for the Angular packages. We’ve made some optimizations for the packages required for an Angular project.This time we decided to tell you a bit more about what’s been done in WebStorm 2017.3. For every WebStorm release, we are making many small and big improvements on the both fronts. The actual speed of processing each file. The amount of data that the IDE needs to index and 2. There are two things that affect the indexing time: 1. It happens when you open the project for the first time, install the project’s dependencies, update from a version control or change the branches, or simply add new files to the project. Optimizing project indexingĪs you may know, to provide code completion and navigation WebStorm has to analyze the project sources. ![]() To learn more about all the new features added in earlier WebStorm 2017.3 EAP builds, please check out these blog posts. You can update via Toolbox App, or download the build here and install it beside your stable WebStorm version. The new WebStorm 2017.3 Early Preview build (173.3531.1) is now available. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |