Hi All,

I was just working on the Browserify task [1] and started on an ITP for builtins [2]. Then I realised that there is actually no javascript in that package. Package.json references builtins.json [3], which has a long list of "requires".

What would people recommend we do here? Should I convert each "require" in builtins to a hard dependency for the browserify package, make node-builtins a meta-package pulling in all the dependencies that are "requires", or just leave builtins to last and check at the end what isn't already pulled in by the other dependencies?

I suppose the first and last ideas are the most efficient and tidy (avoiding a mostly empty package), but may require maintenance effort going forward. We would have to check if builtins has changed every time we update browserify.

Doing the last may end up with good feedback to upstream, by either giving an accurate list of dependencies, or possibly enabling builtins to be dropped.

Regards,

Ross

[1] https://wiki.debian.org/Javascript/Nodejs/Tasks/Browserify
[2] https://github.com/juliangruber/builtins
[3] https://github.com/juliangruber/builtins/blob/master/builtins.json

_______________________________________________
Pkg-javascript-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to