Sometimes people install node.js only to find that there is already an implementation of node.js which seems to have been implemented by CF. What’s up with that?! 🙂
To be clear, you will only see this in CF11 and above, and then only if you chose the “development” profile during CF installation (as discussed here). It’s not that it’s used by the installer itself. Rather, it’s implemented for use with the weinre (mobile development inspection) feature which was also new in CF11 as part of the CF mobile development features.
And what if you want to update that node implementation, for some other use you have in mind? This was discussed in a forum thread where Adobe engineer Vikram indicated it was ok to do so.
Guide
146 posts
As an update to this post from several years ago, I’ll note first that the correct new url for the forum thread mentioned is https://community.adobe.com/t5/coldfusion-discussions/cf11-installation-and-node-js/m-p/6421877. And a link to the cf11 article is available via archive.org at http://web.archive.org/web/20140518130849/http://www.adobe.com/devnet/coldfusion/articles/security-improvements-cf11.htmlÂ
Also, as for the Node that gets implemented under these conditions (developer profile), I can report that for Windows, at least, it’s implemented by default in “C:Program Filesnodejs”–without any prompting or confirmation that this is the location in which it will be installed. But you can confirm that the folder’s creation date/time is the same as that of the CF instance you installed (or installed most recently, if you may install more than one CF version).
If here are some synergies, I want to know about them
I don’t see any, no. And this post was just more to explain the discovery, when I found it last year.
You must be logged in to post a comment.
22 Sep 2025
Las Vegas, NV
