![]() ![]() ![]() The configurations between the 2 versions are identical (I didn't change anything from the defaults) and the difference in the running of the tests is very small, but causes the tests not to run. I upgraded from 2018.2.3 yesterday and can no longer run inline jest tests through the IDE anymore. Unknown option: 'C:\Program Files\JetBrains\WebStorm 2018.2.6\plugins\JavaScriptLanguage\helpers\jest-intellij\lib\jest-intellij-reporter.js' "C:\Program Files\nodejs\node.exe" -require "C:\Program Files\JetBrains\WebStorm 2018.2.6\plugins\JavaScriptLanguage\helpers\jest-intellij\lib\jest-intellij-stdin-fix.js" test -colors -reporters "C:\Program Files\JetBrains\WebStorm 2018.2.6\plugins\JavaScriptLanguage\helpers\jest-intellij\lib\jest-intellij-reporter.js" -verbose "-testNamePattern=^ManageCustomFieldsComponent " -testPathPattern=^D.-custom-fields.manage-custom-fields\.component\.spec\.ts$ but WebStorm passes along arguments to ng test that the jest cli doesn't understand, and I get this: Now, I managed to change the angular.json to the Jest test runner so that indeed, ng test runs Jest and not Karma. The problem is when I try to run individual tests it tries to run ng test. This wasn't too hard to fix, I just went to my Run Configuration and changed the Jest Package back to jest. It looks like by default, WebStorm wants to run ng test now for all tests it used to simply run the jest command, but this changed in my Run Configuration, causing my tests not to work. We appreciate you reporting any bugs and feature requests to our Issue Tracker.I've been using Jest for some time now without a problem, and recently I upgraded to 2018.3 and experienced a number of problems. You can find the full list of bug-fixes and improvements in the release notes.ĭownload PhpStorm 2019.1.2 build 191.7141.52 for your platform on the website or click Update in your JetBrains Toolbox App. Fixed: JDK 11: Response handler doesn’t work (Nashorn is removed) ( WI-45704 +6).Fixed: High CPU usage, code analysis never completes when resolving references from “reselect” module ( WEB-38158 +9).Fixed: Terminal tabs can’t be reordered ( IDEA-202809 +10).Fixed: Move Caret to Matching Brace moves to wrong position ( IDEA-210104 +12).Fixed: Open recent menu doesn’t display project group if any ( IDEA-168223 +55).Thanks a lot to the Laravel community for help with this issue! ![]() The current PhpStorm build brings debugging Blade templates experience back ( WI-46191) for Laravel 5.8.11+. 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. We’ve added support for debugging Blade templates in PhpStorm 2019.1. 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. According to the survey and stats, the main use-case is Docker, which is why we have started with this first. This feature is a subset of a broader request to support Composer via any remote PHP interpreter ( WI-23544). 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: You are now able to run Composer via any Docker image ( WI-45865). In PhpStorm 2019.1.2, this is finally solved. 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. You needed a local PHP setup in order to run it. While PhpStorm supports PHP interpreters via Docker and Docker-compose, it still had some parts missing. 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. 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. In this second minor update for the PhpStorm 2019.1 we are happy to bring you support for Composer via Docker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |