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.
Wizard
146 posts
If here are some synergies, I want to know about them
I don’t see any, no. It was just more to explain the discovery when I found it last year.BTW, I tweaked the content recently merely to check if the update mechanism on the portal would still force the edit to be moderated. It did, for some days. Worse, it also still updates the date of the post, giving the mistaken impression that it’s a new one. Grr.Â
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
