GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)Ĭopyright © 2007 Free Software Foundation, Inc. There is NO WARRANTY, to the extent permitted by law. This is free software you are free to change and redistribute it.

License GPLv3+: GNU GPL version 3 or later GNU bash, version 5.0.17(1)-release (x86_64-apple-darwin18.7.0)Ĭopyright © 2019 Free Software Foundation, Inc. Non-Bundled Plugins:, ,, in., .linessorter,, , pro.bashsupport, .modules,, , ru.Ġ3:02Ğrror running ‘liquibase-install.sh’: Debugging is only possible with GNU Bash, versions 4 or 5, but version 3 was detected VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. What’s Next: WebStorm 2020.2 Roadmap The WebStorm Blog Check out our plans for the 2020.2 release that’s coming this July. Subscription is active until December 26, 2020 We've finalized the roadmap for WebStorm 2020.2 and we're now ready to share it with you. Licensed to Oleg Taranenko Softwareentwicklung / Oleg Taranenko With WebStorm 2020.2 scheduled for the end of July, we’ll continue to move in the same direction that we designated at the end of last year. It would have been good if I could skip steps 1 and 2 for debugging expo projects, but as of WebStorm 2020.2 this is not possible.Latest version of the BashSupport Pro (1.4.11.202) Trial, on latest version of the WebStorm.īuild #WS-202.6397.88, built on July 24, 2020 no need of steps 1 and 2 for non-expo projects. However, if I debug a normal non-expo react-native project in WebStorm, then a break point in WebStorm will be hit without having to set break point in debugger's chrome instance dev tools i.e. Also, at the same time in WebStorm the same break point as in chrome dev tools will be hit, and from this point onward developer can either debug in chrome dev tools or in WebStorm. When expo app reloads in android emulator, then automatically the code will break at break points set in step (2) above. (3) Click on Reload button in debugger's chrome instance (2) Set one or more break points in App.js and/or custom components (this must be done in chrome dev tools instance that was opened in step 1 and NOT in your cod editor/IDE) (1) Open Dev Tools in debugger's chrome instance For expo project debugging to work in WebStorm, the following steps needs to be done.

There are some important points to note when debugging expo project in WebStorm. I was able to finally debug an expo react-native project in WebStorm.

Webstorm 2020.2