PhpStorm & WebStorm 2.0 EAP build 96.1130

A (bit-delayed-due-to-major-internal-changes) fresh weekly build of PhpStorm & WebStorm 2.0 is available:

  • PHP editor performance was improved, both from CPU and memory perspectives. If you find any suspicious behavior when typing php code – do not hesitate to file a report into tracker!
  • PHP library stubs were updated for many extensions, and Parameter inspection will treat non-last optional parameters more properly
  • Language injection in PHP was reworked for predefined SQL & HTML patterns – you may want to open Settings|Language injection and delete all patterns and restart IDE to ensure that you do not suffer any performance penalties from old patterns. And again
  • CSS inspection will treat browser-specific extension more appropriately. Also completion for typical font-family names was added
  • Significant bug fixes, check project issue tracker for more complete changelog

Please note that ALL of this is work in progress and will undergo series of both technical and cosmetic changes during next months.

Download PhpStorm & WebStorm 2.0 EAP build 96.1130 for your platform from project EAP page.

Develop with pleasure!
-JetBrains Web IDE Team

This blog is permanently closed.

For up-to-date information please follow to corresponding WebStorm blog or PhpStorm blog.

This entry was posted in Early Access Preview, PhpStorm, WebStorm. Bookmark the permalink.

4 Responses to PhpStorm & WebStorm 2.0 EAP build 96.1130

  1. Hello, thanks for this new EAP Build. I hope that this new release will provide speed improvement. Do you have an idea when the any frameowrk will be implemented in EAP Builds? Because I have some autocompletition problem with CodeIgniter. A cool feature will be to ignore some HTML error like body not closed, because I have an header and footer seperated.

  2. sewid says:


    the current version (96.1130) has a bug: When having some code like this:

    haveToPaginate()): ?>
    $pager, ‘route_name’ => ‘message_index’, ‘parameters’ => array())) ?>

    It marks the endif and says: “Expected: endif”

    Best regards,

  3. Alexey Gopachenko says:

    @sewid Thanks, we aware of some parser regressions in this build, they are already fixed. Please submit further bug reports to project tracker

  4. sewid says:

    The code has been stripped :-(

    There was a “if (…) :” and an “endif” around the code.

    Best regards,

Comments are closed.