Installed trigger app, installed node.js, trigger says it can't run npm on Mac

New Mac user account. I install the Trigger.io (TriggerToolkit) app for the Mac. It fires up a tab with the apps. I can run the iOS simulator from it - so it is plausibly working installation. I have installed node.js from the node.js website, using the Mac package.

I have node.js as /usr/local/bin/npm (version 1.1.43).

It is found when I type "npm" at a command line.

The path "/usr/local/bin" is on my $PATH.

"/usr/local/bin" is set in my /etc/paths file, system wide.

So the npm executable should be findable by any user, at any time (before or after login, running a terminal, etc).

When I use the web page for the web run, it's OK, until it tries to run npm.

[DEBUG] running run_web((), {})

[DEBUG] Running: npm install

[DEBUG] failed to run npm: do you have Node.js installed and on your path? while running run_web((), {})

[ERROR] failed to run npm: do you have Node.js installed and on your path?

I guess that the problem must be something to do with an assumption about the path for npm. What's the assumption? What can I symlink to make this work?

Note that npm is found by "forge run web". This is something specific to the way that TriggerToolkit.app is working.