[Bug 204577] [NEW MODULE] Mk/Uses/nodejs.mk Framework for NodeJS projects/ports

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204577

--- Comment #19 from Olivier Duchateau <olivierd at FreeBSD.org> ---
(In reply to Mathieu Arnold from comment #17)

@Mathieu, it's still work in progress. It's planned, but not before support of
Grunt (almost finished).

(In reply to yuri from comment #18)

@Yuri, my approach is equivalent to npm -g (modules are installed globally). I
use same way as Ruby's gems, one module = one port (I respect dependencies
found in package.json). I don't understand your comment, because I don't
respect ports philosophy. With my framework, users can define do-install,
post-install targets if he/her wants (see textproc/node-JSONSelect [1] port for
example).
Modules are located into ${LOCALBASE}/lib/node_modules (it's convention for
NODE_PATH). 

You can find complete list here [2], and there're some new modules especially
SocketIO, jison.

Debian and Fedora also follow same approach as me.

About my Mk/Uses/nodegyp.mk, it is independent, it builds only C/C++ extension,
users must define do-install target (except if your module comes from NPM
registry, I defined "build" argument in Mk/Uses/node.mk for convenience).

[1]
https://www.assembla.com/spaces/cozycloud/subversion/source/HEAD/trunk/textproc/node-JSONSelect
[2] https://people.freebsd.org/~olivierd/nodejs-ports.txt

-- 
You are receiving this mail because:
You are on the CC list for the bug.