MacOS – Node Program Runs in Terminal, but Not As a “do shell script” AppleScript

applescriptautomationmacosterminal

I have a call (“mercury-parser” via Yarn, using the full path to the call) that converts Web pages to lines of structured text (the page used in the call describes the service):

/Users/me/.yarn/bin/mercury-parser https://postlight.com/trackchanges/mercury-goes-open-source

If I run it in Terminal (using either /bin/bash or /bin/sh on a 2013 Mac Pro, macOS 10.14.5), I get the proper result: fourteen lines of structured text from the Web page.

However, the very same call returns an error when run as a single-line, “do shell script” AppleScript:

do shell script "/Users/me/.yarn/bin/mercury-parser https://postlight.com/trackchanges/mercury-goes-open-source"

The error returned is:

error "env: node: No such file or directory" number 127

FWIW, here are both my .profile and my .bash_profile texts (the latter created solely to try and solve this quandary), that should not be necessary, given that the full path to the call is being specified, specifically to avoid such an error:

export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH"

export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"

[[ -s $HOME/.nvm/nvm.sh ]] && . $HOME/.nvm/nvm.sh  # This loads NVM

source ~/.nvm/nvm.sh

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm

What do I have to do to get the call to run as an AppleScript?

[2019.6.26 at 11:25:45PM: Edited in an attempt at clarification.]

2019.6.27 at 1:36:57PM: Per Mark’s suggestion:

Thank you, Mark; I duplicated my .[bash_]profile, renamed it to “.bashrc”, and added “bin/bash” to the call:

do shell script "bin/bash; /Users/RF/.yarn/bin/mercury-parser https://postlight.com/trackchanges/mercury-goes-open-source"

However, (after a reboot) I still get the same error:

error "env: node: No such file or directory" number 127

Thoughts?

Best Answer

This was solved by KniazidisR at https://macscripter.net/viewtopic.php?pid=196447#p196447

set nodePath to "/usr/local/Cellar/node/12.5.0/bin/node "
set mercuryParserPath to "/usr/local/bin/mercury-parser "
set pageURL to "https://postlight.com/trackchanges/mercury-goes-open-source"

do shell script nodePath & mercuryParserPath & pageURL

Related Solutions

Many programs notify me that “grep/sed/uname/… not found”; some run, some don’t. My system(?) path is damaged, how to go about a diagnosing it

Your question is unclear as it seems to ask several things. However the issue re launching from the Dock can be answered.

The Dock does not call a shell. .profile and other startup scripts are only run when Terminal.app or similar starts a shell or you run a shell script via launchd etc.

To change the path used for Apps launched from the Dock, Finder or other GUI then you need to change the path your Workspace uses this is in ~/.MacOSX/environment.plist e.g. mine is

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>WAFDIR</key>
  <string>/Users/mark/src/third_party/git-svn/waf</string>

  <key>PATH</key>
  <string>/Users/mark/bin:/Users/mark/env/bin:/Users/mark/usr/local/bin:/usr/local/bin:/opt/local/bin:/usr/local/git/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/libexec/binutils:</string>
</dict>
</plist>

Also have a look at this question.

MacOS – Characters do not echo in OS X terminal unless I hit the delete key

Your prompt is messed up, specifically PS1:

PS1=$[\033]0;37m]

that's missing a lot of escape characters (\e[) needed for the colors (and most useful parameters for a PS1). That's also why you get the 37m in the terminal window title. Try setting it to something different by running:

export PS1="\e[0;31m[\h:\W \u]\$\e[m "

and see if that works. It should give a red (thats \e[0;31m) prompt showing hostname (\h), current working directory (\W) and logged in user (\u) inside brackets [] and the bash exit status of the previous command (\$). Note that at the end the color is reset to the default of the session with \e[m .

If the above worked, you only have to find out from which configuration file your "bad" PS1 comes from: look for an "export PS1=" line in ~/.profile, ~/.bash_profile, ~/.bashrc, (as M K already suggested in his answer) and put in the above version.

There are a lot of answers around here with helpful colors codes and inputs for configuring the PS1, like this one for example.

Best Answer

Related Solutions

Many programs notify me that “grep/sed/uname/… not found”; some run, some don’t. My system(?) path is damaged, how to go about a diagnosing it

MacOS – Characters do not echo in OS X terminal unless I hit the delete key

Related Question