How should we name node-js ports ?

Julian Elischer julian at
Sat May 20 06:57:14 UTC 2017

On 14/5/17 8:16 pm, Rodrigo Osorio wrote:
> Hi,
> I have a bunch of nodejs ports to add, most of them as dependencies,
> and I wonder if we can find a naming standard like adding  'node' or
> 'node-js' prefix in the name ; I personally prefer 'node'.
> As a result a port who install the node package xxx will be named 
> 'node-xxx'
> Does it sounds good to you ?
> Thanks for your time,

this brings up the whole question of whether we should package these 
things ourselves anyhow.
python and perl  have their own schemes (pip et al.)  and with npm 
(and others) node is no exception.
it seems that to chase these packages down manually is a never ending 
maybe the way we should handle it is to have a generic  "handover to 
external package manager" feature,
so that we somehow let npm (or whatever) do it ting but then take the 
output result an put it into our database.

At $JOB we have the issue of many many node modules for our new gen UI 
and it causes us a great headache.

> -- rodrigo
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to 
> "freebsd-ports-unsubscribe at"

More information about the freebsd-ports mailing list