Calling Node.js script from Rails app using ExecJS

Question

I have a Rails application that needs to run a node script. I imagine that using the ExecJS gem is the cleanest way to run JavaScript from a Rails app. However, so far, ExecJS has proved to be very frustrating to use.

Here is the script I need to run:

// Generated by CoffeeScript 1.7.1
(function() {
  var PDFDocument, doc, fs;
  fs = require("fs");
  PDFDocument = require('pdfkit');
  doc = new PDFDocument;
  doc.pipe(fs.createWriteStream('output.pdf'));
  doc.addPage().fontSize(25).text('Here is some vector graphics...', 100, 100);
  doc.save().moveTo(100, 150).lineTo(100, 250).lineTo(200, 250).fill("#FF3300");
  doc.scale(0.6).translate(470, -380).path('M 250,75 L 323,301 131,161 369,161 177,301 z').fill('red', 'even-odd').restore();
  doc.addPage().fillColor("blue").text('Here is a link!', 100, 100).underline(100, 100, 160, 27, {
    color: "#0000FF"
  }).link(100, 100, 160, 27, 'http://google.com/');
  doc.end();
}).call(this)

From my Rails console, I try this:

[2] pry(main)> file = File.open('test.js').read
[3] pry(main)> ExecJS.eval(file)
ExecJS::ProgramError: TypeError: undefined is not a function
from /Users/matt/.rvm/gems/ruby-2.1.0/gems/execjs-2.0.2/lib/execjs/external_runtime.rb:68:in `extract_result'

Note that I can run this script successfully using 'node test.js' and I am also able to run run the script using the backtick syntax Ruby offers:

`node test.js`

But that feels like a hack...

Sounds like a great use case for microservices. Have a Node.js server attending requests made from the Rails server! — deprecated, Dec 14 '15 at 16:07
This is unrelated to the question, but relevant to the code. If you're trying to create a pdf from a rails app, why not use ruby libraries like 'prawn'? — hamitron, Dec 15 '15 at 16:13
@vemv prawn is terrible when it comes to render runtime charts in PDF. Here is some analysis. https://aarvy.me/blog/2019/09/11/rails-6-charts-pdf-generation-gems-availability-and-comparison/ — Rajan Verma - Aarvy, Dec 28 '19 at 04:29

score 3 · Answer 1 · answered Oct 23 '15 at 05:46

3

It's erroring out because require() is not supported by EvalJS. 'require' is undefined, and undefined is not a function. ;)

answered Oct 23 '15 at 05:46

seanmakesgames

773
1
7
14

score 2 · Answer 2 · answered Apr 04 '14 at 02:04

2

I'm not sure of the answer but maybe you need to precise the exec_js_runtime environment variable to be node.

Something like ENV['EXECJS_RUNTIME'] = 'Node' You can try to put it in the config/boot.rb or just to define the EXECJS_RUNTIME in your environment, something like export EXECJS_RUNTIME=Node

Hope it helps

answered Apr 04 '14 at 02:04

Uelb

3,947
2
21
32

I don't think the is the problem. I definitely have a working node installation and I am able to run 'ExecJS.eval("1 + 1")' without any problems. Thanks anyway. – matt walters Apr 04 '14 at 02:50
Yeah but are you sure that exec js is using node and not another runtime ? – Uelb Apr 04 '14 at 02:52
What is the result of `ExecJS.runtime` ? – Uelb Apr 04 '14 at 02:55
[18] pry(main)> ExecJS.runtime => # – matt walters Apr 04 '14 at 03:22
The example doesn't work according to `ExecJS` people https://github.com/sstephenson/execjs#faq they say you should use `commonjs` gem, but it feels unfinished https://github.com/cowboyd/commonjs.rb - the OP's example script executes without error but there's no output – bbozo Dec 15 '15 at 18:39

bbozo · Answer 3 · 2015-12-15T19:05:40.670

ExecJS people say use commonjs.rb https://github.com/cowboyd/commonjs.rb

Why can't I use CommonJS require() inside ExecJS?

ExecJS provides a lowest common denominator interface to any JavaScript runtime. Use ExecJS when it doesn't matter which JavaScript interpreter your code runs in. If you want to access the Node API, you should check another library like commonjs.rb designed to provide a consistent interface.

But this doesn't work basically. The require acts completely erratically - I had to execute npm -g install pdfkit fs between env = and env.require in

require 'v8'
require 'commonjs'
env = CommonJS::Environment.new(V8::Context.new, path: ::Rails.root )
env.require 'script'

for the module lookup to work O.o and if I tried pointing path to the node_modules folder then it would be impossible for the gem to find script (not to mention that the #new and require are basically the only documented methods - only methods afaik - and #new is misdocumented :P)

Your options as far as I can tell:

system(node ...) - you can use Cocaine to escape some gotcha's (piping output, error handling, performance tweaks, ...) and run a cleaner syntax - this is not as bad as it looks - this is how paperclip does image postprocessing (imagemagick system package + cocaine) so I guess it's very stable and very doable
expose to web api and run a separate worker on a free heroku dyno for example to do this and similar stuff you want to do with node libs
use prawn :)

score -3 · Answer 4 · answered Aug 20 '19 at 18:00

-3

Get rid of ExecJS and anything that depends on ExecJS. I tried all the other suggestions, but this actually fixed it.

ES6 has been around since 2015. Any tool worth using supports it by now. MICROSOFT EDGE supports it by now. Seriously.

answered Aug 20 '19 at 18:00

Andrew Koster

1,550
1
21
31

Calling Node.js script from Rails app using ExecJS

4 Answers4

Linked