Closed AdamBD closed 5 years ago
hi @AdamBD
did you create a customisation file for preferences or bin name?
Hi
/usr/local/bin$ ll | grep "pstorm" rwxr--r-- ABD staff 3 KiB Thu Oct 17 13:49:27 2019 pstorm
I have a script in /usr/local/bin registered as pstorm
, which calls to the location of where PHPstorm is under the JetBrains tool box in the /Applications folder.
Then in the Toolbox I set this path
Is this the correct way to do it?
Hi,
On tool box settings the shell scripts location should be /usr/local/bin
, and in PhpStorm settings only pstorm
(or phpstorm
)
But the issue seems to be before the check of the shell script.
Can you check your workflow, on Alfred, the PhpStorm "box" should be like this:
Hi,
I've made the changes you suggested and checked the alfred config for the pstorm node. All looks as in your screenshots. Now when I try running the workflow I get the following new error:
TypeError: util.getSystemErrorName is not a function
at getCode (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/lib/error.js:11:16)
at makeError (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/lib/error.js:50:35)
at Function.module.exports.sync (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/index.js:187:17)
at Function.module.exports.commandSync (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/index.js:224:15)
at Object.viaWorkspaceXml (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project/name.js:57:30)
at Object.getProductName [as get] (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project/name.js:88:43)
at buildItem (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:7:28)
at paths.forEach.path (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:40:20)
at Array.forEach (<anonymous>)
at Object.getItems (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:39:11)
- JetBrains - Open Project - v3 1.1.4 Alfred 4.0.5 darwin 18.5.0
@AdamBD
can you try to uninstall / install again the workflow, please?
@bchatard sure thing. Did so just now:
TypeError: util.getSystemErrorName is not a function
at getCode (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/lib/error.js:11:16)
at makeError (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/lib/error.js:50:35)
at Function.module.exports.sync (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/index.js:187:17)
at Function.module.exports.commandSync (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/node_modules/execa/index.js:224:15)
at Object.viaWorkspaceXml (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project/name.js:57:30)
at Object.getProductName [as get] (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project/name.js:88:43)
at buildItem (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:7:28)
at paths.forEach.path (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:40:20)
at Array.forEach (<anonymous>)
at Object.getItems (/usr/local/lib/node_modules/@bchatard/alfred-jetbrains/src/project.js:39:11)
JetBrains - Open Project - v3 1.1.4
Alfred 4.0.5
darwin 18.5.0
Same issue im afraid. Looks like I may just have to drop it at this point.
can you check your node version please?
Node: v9.2.0
@AdamBD
ok it's seems that your node version is not compatible with execa
because of missing function in node 9.2.0... (see https://github.com/sindresorhus/execa/issues/318)
The function has been added in 9.7.0 and backported in 8.12.x but not in previous 9.x...
Can you upgrade to at least node 9.7? Or maybe latest LTS version?
If it's solve your issue I will update the documentation and tests about the version
That did it!
Works perfectly now. Really awesome workflow BTW. Makes development such a pleasure with PHPstorm
@AdamBD thanks for your feedback!
Describe the bug Hi,
I updated versions following this issue: https://github.com/bchatard/alfred-jetbrains/issues/59
and now run into the following new one: