search

typesafehub / js-engine

A JavaScript Engine Library - provides an abstract of a means to execute JavaScript code where no browser is involved.
Other
72 stars 20 forks source link

Optional command path declarations #15

Closed huntc closed 10 years ago

huntc commented 10 years ago

Engines now allow their full path to be supplied instead of relying on each command being available to the environment's path.

This change enables https://github.com/sbt/sbt-js-engine/issues/2

jroper commented 10 years ago

So, the actual interface for a Play end user to specify the path is I guess going to be in the sbt-js-engine plugin?

huntc commented 10 years ago

So, the actual interface for a Play end user to specify the path is I guess going to be in the sbt-js-engine plugin?

yes:

export SBT_OPTS="$SBT_OPTS -Dsbt.jse.command=/usr/local/bin/node"

or 

JsEngineKeys.command := Some(file("/usr/local/bin/node"))