PhpStorm 2017.1 Early Access Program is Open

Posted on by Anna Lebedeva

Today we start the Early Access Program for PhpStorm 2017.1 (EAP). A fresh build 171.1834 is available for download and in JetBrains Toolbox App.

What is Early Access Program?

Early Access Program allows you to try pre-release versions of our software to evaluate features that will be added in the next release. It is important to distinguish EAP from traditional pre-release software. Please note that the quality of EAP versions may at times be far below even usual beta standards. If you are looking for a stable version of PhpStorm, please visit our site.


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

New code highlights

We’ve added new row highlights, such as highlighting of all extended/implemented methods, places where an import is used, and places where an exception is thrown (for try, catch, and @throws). This way your code is even more visual, and it’s easier to grasp the important details. To use this feature, simply place the caret on extends, implements, use, catch or @throws.

Here the caret is placed on the @throws keyword:

And here the caret is on the use keyword:

Parameter hint for method and function calls

The editor has also been improved, with parameter hints now showing for literals and nulls used as method arguments. These hints make code much more readable, helping you understand the semantics of specific methods. This feature is still experimental so do let us what you think about it!

For an example of how it works in IntelliJ IDEA, click here.

New quick-fix for undefined variables

We’ve added a new quick-fix for resolving undefined variables by declaring it as imported in closure.

Other features worth noting:

  • Support for emoji in the editor (rendered as color images on macOS and as monochrome characters on Windows and Linux)
  • Zero-latency typing is now enabled by default
  • Better Mocha testing experience
  • Integration with the Angular language service
  • Faster start with linters

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

  • Rename refactoring of parameter breaks PHPDoc if Keep blank lines in PHPDoc is disabled and Blank lines around parameters is enabled: WI-23666
  • Conflicting import is not detected (functions, consts, classes): WI-23908

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

Download PhpStorm 2017.1 EAP build 171.1834 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

Comments below can no longer be edited.

30 Responses to PhpStorm 2017.1 Early Access Program is Open

  1. Regular Labs says:

    December 22, 2016

    I love the paramater hints. But why only on literals?
    I’d love to see this when passing variables too.
    Maybe a (default) option to hide the hint when the parameter name is the same as the variable name, like:
    str_replace( search: ‘foo’, replace: ‘bar’, subject: $string);
    str_replace( $search, $replace, subject: $string);
    str_replace( $search, $replace, $subject);

  2. Regular Labs says:

    December 22, 2016

    PS: The Blacklist for the Parameter Hints doesn’t seem to work. Still seeing hints in define(*,*)

  3. Christopher Heuer says:

    December 22, 2016

    There doesn’t seem to be any way to change the style of the parameter hints, mine are showing slightly lower than the baseline of the rest of the text.

    I like them though!

  4. Thomas Schulz says:

    December 22, 2016

    For parameter hints we use inline comments, but they are not “supported” by PHP formatter:

    – Visible outside IDE (like code review tools)
    – Visible to users of other IDEs
    – can be added on case-by-case

    – intention and quick-fix for literal argument
    – refactoring the parameter name also changes parameter hint comments

    • Maxim Kolmakov says:

      December 23, 2016

      Please create a feature request at: but it will be a very low priority feature since such convention is really rare used. If I’m mistaken here please provide a reference to any popular open source project. In my opinion PhpStorm type of parameter hints are more convenient since they don’t require any manual work and don’t pollute VCS.

  5. Tomasz Ksion says:

    December 23, 2016

    Is it possible to change colors & fonts of type hints? It looks like this in my editor:

  6. Haszpra Olivér says:

    December 24, 2016

    hacklang support would be the best! even just the support for < ? hh tag would be great! yes there are big projects written in hack…

    • Maxim Kolmakov says:

      December 28, 2016

      We’ve decided to postpone support of Hack. Please read our explanation here:

      • Chase Jenkins says:

        March 10, 2017

        This was a reasonable answer when the blog was posted in 2015, but now it’s been nearly 2 years. The reasoning that was used in that blog post is now out of date. What’s happening with Hack support now?

        • Maxim Kolmakov says:

          March 13, 2017

          PHP has developed quite a bit in the last 2 year as well in terms of performance and type strictness. Of course, there are still some areas where PHP lags behind (like generics, for example) but, unfortunately, we don’t see a huge enough interest in Hack at the moment. The situation can change in future and we will reconsider the possibility to support.

  7. Иван Челищев says:

    December 27, 2016

    There is problems with fonts. I use Ubuntu 16.04 and font Consolas. Previous PhpStorm version works good:

    PhpStorm 2016.3.2 Build #PS-163.10504.2, built on December 20, 2016
    Licensed to Bitrix / Ivan Chelishchev
    You have perpetual fallback license for this version
    Subscription is active until April 26, 2018
    JRE: 1.8.0_112-release-408-b6 amd64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

    When I upgraded, IDE did not find Consolas as monospaced font.

  8. Иван Челищев says:

    December 27, 2016

    There is problems with fonts. I use Ubuntu 16.04 and font Consolas. Previous PhpStorm version works good:

    PhpStorm 2016.3.2 Build #PS-163.10504.2, built on December 20, 2016
    You have perpetual fallback license for this version
    JRE: 1.8.0_112-release-408-b6 amd64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

    When I upgraded, IDE did not find Consolas as monospaced font.

    • Maxim Kolmakov says:

      December 28, 2016

      There could be many reasons for the issue. Please contact our support team via Help->New Support Request.

    • Fred says:

      March 24, 2017

      Same problem form me, did you solve the issue ?

  9. bernard robert says:

    December 28, 2016

    EAP 64BIT is missing?I am trying to install 64bit but it appeared not avalaible.

  10. Михаил Красильников says:

    December 29, 2016

    У них куча открытых багов по юзабили, а они эмодзи добавляют. А мы за это ещё и платим. И годами ждём, когда же эти баги исправят…

    • Maxim Kolmakov says:

      December 29, 2016

      We’re really sorry that there are some important issue that are not fixed yet but we’re working on the,

      According to your previous comments the issues that annoy you are from VCS subsystem and Project opening. We have a very large team that works in platform and different people work on different issues. Their responsibility areas are rarely overlap. I’m telling all this to point out that implementing emoji doesn’t slow down other areas. Besides emoji was a very voted feature which has more than 200+ votes.

  11. Mark P says:

    December 29, 2016

    Parameter hints are showing for non-literals, but I don’t have that option checked:

    What’s the deal? It’s not terrible, but I’d expect the hint to *not* show if I don’t have “Show for non-literals…” checked.

  12. Maveius says:

    March 14, 2017

    When I run Codeception from PHPStorm I have problem with zend session…

    Session must be started before any output has been sent to the browser; output started in C:homecodelottesiven

    run [–report] [–html [HTML]] [–xml [XML]] [–tap [TAP]] [–json [JSON]] [–colors] [–no-colors] [–silent] [–steps] [-d|–debug] [–coverage [COVERAGE]] [–coverage-html [COVERAGE-HTML]] [–coverage-xml [COVERAGE-XML]] [–coverage-text [COVERAGE-TEXT]] [–no-exit] [-g|–group GROUP] [-s|–skip SKIP] [-x|–skip-group SKIP-GROUP] [–env ENV] [-f|–fail-fast] [–no-rebuild] [–] [] []

    but run from console without problems. Please repair.

    • Maxim Kolmakov says:

      March 14, 2017

      Please create a support request with details about your project (Help->New Support Request).

      • maveius says:

        March 16, 2017

        Ok. It’s done. My previous comment should be removed. Thanks!.


Subscribe for updates