This is very interesting theme :)
I believe that Safe has big plans with the JavaScriptCaller in NodeJS mode, because before 2016, the JSCaller wasn't particularly useful. Not sure though if and how they prioritise these plans...
The NodeJS mode is still very beta, but has huge potential indeed. There already is an API for it and you can find the documentation in your FME program folder under fmeobjects\\nodejs\\apidoc\\index.html. However, at the moment it's far less powerful than the Python API. You can only read and write feature attributes, but you can't read any geometries, for instance.
@sander_s, thanks for sharing that. I hadn't tried working with geometry yet using JavaScript, but did do a proof of concept manipulating tabular LRS data with the JavaScriptCaller which worked out ok.
I had looked at the documentation under fmeobjects\\nodejs\\apidoc\\index.html, but it was quite sparse. The object model is very consistent with the Python model so I generally look at that.
I hope the folks from Safe weigh in here too when they get a chance. While I understand custom programming transformers isn't necessarily their first port of call, we have some unique business cases for data manipulation that will require it, and I'd love to do it using JavaScript.
Hi @t2
I have played with the node option with the JavaScript caller a little bit.
I found that to use external libraries I had to install npm independently and install the packages, then reference their full paths in the JS code inside the transformer to use them.
I am not too sure about the future of it internally, but if you have any thoughts/ideas I would definitely add them to our ideas exchange!
@jlutherthomas,
Hi. I didn't have to hardcode the require path, because I inspected the module object to see what default paths they set up. To do this, you can do something as simple as this in the JavaScriptCaller:
console.log(module.children)
From this you can observe the node_modules that are added. On a windows machine for example, the path: 'c:\node_modules' is in the require search path, and creating that directory and adding a library there allows you to require it without hardcoding 'c:\node_modules\lodash' or whatever.
Whether this is the correct approach from FME's perspective is unknown, since they didn't publish any documentation on this. Certainly wouldn't want to put libraries in the "Program Files" directory for sure, so they would need to either let one configure the environment with the path, or standardize an approach.
Also, you don't have to (but probably should) install node independently, since they are including node with their distribution.
Anyway, that is as much as I have hacked out of this so far.
it would be great if fme could wrap npm search and npm install in a transformer! Also, did anyone get the nodejs engine working on fme server with external modules?
