Yes.
The launch editor functionality does not work for Webstorm 2017.3.2.
As per Webstorm docs, the command should specify the workspace too.
After some debugging, I saw the https://github.com/facebookincubator/create-react-app/blob/4434467a438c3d431a5169038a5f481bbf763efe/packages/react-dev-utils/launchEditor.js#L130 initialization, and I don't see anywhere where the variable is reinitialized.
Yes. Current version I'm using is 4.2.0
The only relevant description can be found in the Advanced Configuration, therefore theREACT_EDITOR - which I didn't override.
node -v:npm -v:yarn --version (if you use Yarn):npm ls react-scripts (if you haven鈥檛 ejected): Then, specify:
Relevant file is opened in Webstorm.

Many thanks!
I couldn't reproduce this behavior with Webstorm 2017.3.2. Also, it seems Webstorm does work without specifying workplace as far as path2 is absolute or relative to current working directory. In your case, the problem is somehow it has failed to figure out the current working directory correctly. Can you please try the following command and let us know how it works?
webstorm --line <some-line-number> <path-to-a-file-relative-to-current-working-directory>
@tharakawj thanks for having a look.
If I use the relative path /Applications/WebStorm.app/Contents/MacOS/webstorm --line 3 ./src/App.js, I have the same error, as described above.
Indeed, if I use the absolute path of the file, it works.
One more detail, I am using the zsh as my default shell.
If the command with relative path doesn't work, I think there is a problem in your setup.
Are you always using the full path to the webstorm application without creating Command Line Launcher? Then probably that's the issue. If webstorm command doesn't work, then you need to manually create the launcher in WebStorm: Tools -> Create Command Line Launcher...
@tharakawj Yes, that was it.
Many thanks!
Most helpful comment
If the command with relative path doesn't work, I think there is a problem in your setup.
Are you always using the full path to the webstorm application without creating Command Line Launcher? Then probably that's the issue. If
webstormcommand doesn't work, then you need to manually create the launcher in WebStorm:Tools -> Create Command Line Launcher...