Mastodon developers instruct users to use node6. Until recently though, net-im/mastodon worked fine with www/node, but there is a FreeBSD-specific bug with node8 now preventing users from getting the latest net-im/mastodon up and running .
Hopefully a new node8 release will come soon, but in the meantime, could we add options to www/npm to allow it to be built with www/node6? The other two net-im/mastodon dependencies that pull in node (devel/rubygem-execjs and www/yarn) have the option to choose the node version, so users will at least be able to get Mastodon up and running if they build these three packages with non-default options.
I know this has been discussed in the past , but I now feel making www/node6 the default for all of the latest node ports is best for users. It's what the node developers recommend "for most users" on their site and node6 seems more stable. Could you share your thoughts on this?
 After installing net-im/mastodon, users have to install node modules (under www/mastodon/node_modules) manually with yarn install. (That's not ideal, but packaging several hundred node modules will be challenging. An omnibus package containing all the node modules might make sense, but there are binaries, so care must be taken.) It's during yarn install that a compile error occurs when building node-sass. See http://okturing.com/src/1525/body for the error.
 The rationale for recently switching www/yarn from using www/node6 to www/node by default was because other node-related ports were pulling in www/node and this was causing conflicts.