Closed luke-eisenbraun closed 10 years ago
I will check this out sometime this week. PR welcomed.
I have fixed the issue with using a local/global/custom CasperJS binary in v0.3.9.
export a variable CASPERJS_EXECUTABLE
which points to the executable you wish to load.
I have a fork of the Casperjs repo which has some customized functions added to it. When using npm install, grunt-casper pulls in the newest version and uses that instead of the one I have installed on our build agents.
Right now I have a script that goes in and and modifies the grunt.util.spawn to run with the old 'casperjs' cmd which solves the issue.
Could we get functionally similar to phantomjs in which it looks for a currently installed version and uses that, then defaulting to the npm managed version if nothing is found in the path?