PhpStorm 2019.1.2 is released

PhpStorm 2019.1.2 build 191.7141.52 is now available!

In this second minor update for the PhpStorm 2019.1 we are happy to bring you support for Composer via Docker. This release also contains a Blade templates debugging fix, and a bunch of other bug fixes and improvements for PHP, the Web, and includes all the latest improvements made to the IntelliJ Platform.

Support Docker for Composer execution

The usage of containerized environments by PHP developers is steadily growing by roughly 12% each year – from 18% in 2017, to 30% in 2018, to 42% in 2019, according to The State of Developer Ecosystem Survey. While PhpStorm supports PHP interpreters via Docker and Docker-compose, it still had some parts missing. One of these is Composer integration. You needed a local PHP setup in order to run it. But it could be that this differs from the one you have in your containerized dev environment, or you might not even have a local PHP interpreter at all both of which might cause problems.

In PhpStorm 2019.1.2, this is finally solved. You are now able to run Composer via any Docker image (WI-45865).

Under Preferences | Languages & Frameworks | PHP | Composer you can find a new Docker radio button option, where you’ll be able to configure the Docker server (this is not a PHP server), as well as provide an image, the Composer executable name, and the container options:

composer-via-docker

This feature is a subset of a broader request to support Composer via any remote PHP interpreter (WI-23544). According to the survey and stats, the main use-case is Docker, which is why we have started with this first. We would like to hear from you on how you like the current implementation, then based on this feedback we will try to improve and expand it to the other use-cases.

Support new format of Blade debug info

We’ve added support for debugging Blade templates in PhpStorm 2019.1. Due to a bug, the debug info format, which is needed for PhpStorm to map compiled files to original templates, since a change was made in Laravel 5.8.11. The current PhpStorm build brings debugging Blade templates experience back (WI-46191) for Laravel 5.8.11+.
Thanks a lot to the Laravel community for help with this issue!

Other notable changes:

  • Fixed: Open recent menu doesn’t display project group if any (IDEA-168223 +55)
  • Fixed: Move Caret to Matching Brace moves to wrong position (IDEA-210104 +12)
  • Fixed: Terminal tabs can’t be reordered (IDEA-202809 +10)
  • Fixed: High CPU usage, code analysis never completes when resolving references from “reselect” module (WEB-38158 +9)
  • Fixed: JDK 11: Response handler doesn’t work (Nashorn is removed) (WI-45704 +6)

You can find the full list of bug-fixes and improvements in the release notes.


Download PhpStorm 2019.1.2 build 191.7141.52 for your platform on the website or click Update in your JetBrains Toolbox App.

We appreciate you reporting any bugs and feature requests to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Release Announcements and tagged , , , , , . Bookmark the permalink.
  • https://twitter.com/michabbb Michael Bladowski

    Support Docker for Composer execution: finally! https://media3.giphy.com/media/13mbTHVskEHyGA/giphy.gif

  • Greg

    “Fixed: Terminal tabs can’t be reordered (IDEA-202809 +10)”

    I think it’s not fixed, at least not on Linux 😉 As you couldn’t drag them you cannot do that now after update either:

    PhpStorm 2019.1.2
    Build #PS-191.7141.52, built on May 8, 2019
    Licensed to *****
    You have a perpetual fallback license for this version
    Subscription is active until *****
    JRE: 1.8.0_202-release-1483-b49 amd64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    Linux 4.15.0-46-generic

    • Maxim Kolmakov

      In 2019.1.2 it is possible to reorder terminal tabs with Ctrl+Shift+Left/Right (on Mac: Cmd+Shift+Left/Right). These actions are also available in context menu opened on terminal content.

      To drag-and-drop terminal tabs nicely, please vote for https://youtrack.jetbrains.com/issue/IDEA-71490.

  • Yann

    Good introduction of Composer with Docker !
    Maybe a configuration closer to the Quality Tools model (with default project interpreter) could be a good improvement when Composer is embedded with PHP container so it will be less configurations with New project settings on many pojects !
    I’m not sure how to deal with private repo, with solution like SSH agent forwarding some advanced options for environment variables or for running might be necessary to complete such feature.

    Keep up doing great job on Docker support 😉

  • Martin Melka

    Composer-in-docker — which user is used when doing that? I am guessing root, in which case this might not work for everybody… like us :(

  • Koci Niewolnik

    I have problem with composer with docker. How to setup own SSH key if some requieres are from private repositories?

    update --no-interaction --ansi
     Deprecation warning: require.willdurand/Negotiation is invalid, it should not contain uppercase characters. Please use willdurand/negotiation instead. Make sure you fix this as Composer 2.0 will error.
     Loading composer repositories with package information


      [RuntimeException]
      Failed to execute git clone --mirror 'git@bitbucket.org:autodata-group/malachite-common.git' '/root/.composer/cache/vcs/git-bitbucket.org-autodata-group-malachite-common.git/'

      Cloning into bare repository '/root/.composer/cache/vcs/git-bitbucket.org-autodata-group-malachite-common.git'...
      Host key verification failed.
      fatal: Could not read from remote repository.

      Please make sure you have the correct access rights
      and the repository exists.