Hi Stuart, > > Simplest is usually to fetch via npm out-of-band, tar it up and provide > a tar containing the files. >
Great, thanks for clarifying. It feels a bit awkward having to do this but I can't say I can think of a better approach. Unlike Perl, it seems that all the scatty Node.js NPM dependencies don't have their own ports. > > No committed port does this, it is not permitted to fetch during the > build stage. > Yeah, it seems I was imagining things when I first prepared my port. Also, looking at the Emscripten port for FreeBSD, to avoid this, they skip the NPM dependencies step entirely (and thus some optimizations are disabled). Best regards, Karsten
