PhpStorm 2017.3 EAP 173.2941.8

The new PhpStorm 2017.3 EAP build (173.2941.8) is now available! You can download it here or via JetBrains Toolbox App. Or, if you have the previous PhpStorm 2017.3 EAP build (173.2463.17) installed, you should soon get a notification in the IDE about a patch update.

This build delivers new features, bug fixes, and improvements for PHP and the Web, and includes the latest improvements in IntelliJ Platform.

Performance Improvements

We’ve been working hard on performance improvements in the last two EAPs and we’ve managed to decrease typing latency in the very complex PHP files. For example, we’ve measured the following changes in mPDF main file (38k lines, a mix of PHP/JS/HTML):

Min Delay (ms) Max Delay (ms) Average Delay (ms)
PhpStorm 2017.3 EAP 15.4 46.2 27.3
PhpStorm 2017.2 124.9 210.4 134.6

The measurement was performed using the amazing tool, Typometer, that captures the delay between key press action and its appearance on the screen. As you see the delays have decreased by a factor of 4.

The work is still in progress and we hope to boost performance even further.  If you have particular examples of files that are sluggish in PhpStorm, please comment or create an issue in YouTrack.

Composer Log

In this build, we’ve implemented a Composer Log console. Before all the messages about composer actions and related settings changes were shown in the Event Log, which was overwhelming and not always informative. Now we’ve made a dedicated Composer Log for all Composer related actions and notifications in the project. As a bonus, you can also rerun all actions right from the Log. The Composer Log can be opened from the composer.json editor panel or from the Event Log when you get a first Composer notification. Check it out and let us know what you think!


From the platform side the update brings:

  • Better synchronization of your settings across devices (more details here)
  • Mocha test runner: support –watch option (WEB-11104)

Apart from new features, this build has many bug fixes, including these:

  • Parse exception while converting JSON to object class working with GitHub (IDEA-178764)
  • Only some foreign key edges are shown in the diagram (DBE-2130)
  • Postgres: Database console sets different timezone in session that PGAdmin (DBE-2996)

See the full list of bug-fixes and improvements in our issue tracker and the complete release notes.

Download PhpStorm 2017.3 EAP 173.2941 for your platform from the project EAP page or click “Update” in your JetBrains Toolbox App. And please do report any bugs and feature request to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Early Access Program, Newsletter. Bookmark the permalink.
  • Thomas Schulz

    What happened to the UI font? It’s smaller now and buttons/toolbars etc got smaller :-(

    (Running on Windows 10 with default DPI / 100% UI scale)

    • lawkadw

      +1, Windows 7, non-retina monitor, something is wrong with UI font and file icons/menu icons, they are tiny now!

      • lawkadw

        somehow adding a “-Dhidpi=false” into “phpstorm64.exe.vmoptions” and resetting editor font to Monospaced 12 default made it more or less readable / viewable

        • Vladimir Luchansky

          @Thomas Schulz @lawkadw Thank you for this observation. We already investigating this under – please vote for it with thumb up button to receive notifications about further progress.

  • FotoKrakus

    Thanks :-)

  • Venimus

    I have this visual issue when using global search and replace. This happens when the “found” term is soft-wrapped to new line I

    • Dmitry Tronin

      Can’t find similar reports. Does the same occur in other projects? If it does – feel free to submit a report at

      • Venimus

        Hi, my bad seems this was for the previous 2017.2. Looks like the replace dialog is redesigned in 2017.3 and this is no longer reproducable as there are no soft-wraps in the preview (which seems like a regression)

  • Mark P

    These performance improvements seem to come at the cost of accuracy. Almost all of these hints are wrong. The `if` and `else` say “statement has no body”, it’s saying my “start” array key is a dupe, but it isn’t, `$delDay` is unused, but it is used, `$numCopies` is undefined, but it is defined… everything’s wrong and it’s not playing catch up either — it’s done checking. Past few EAPs have all had this problem.

    • Eugene Morozov

      It seems that the indices were broken. Does this happen again after indexes invalidation?

      • Mark P

        Yes. It might work for a bit after invalidation but it breaks again after a few minutes of coding.

        • Eugene Morozov

          Any 3rd party plugins installed? Please disable them all and check if it runs better.
          We’ve seen the Symfony plugin breaking indexes lately.