update package xml as a prep for npm publish

[jihoonl]

#127

I was intentionally renaming from roslibjs to roslib because I thought .js extension already implies it is javascript module. Would it be better to publish as roslibjs for consistency?

[megawac]

This will break node, main is for usage in nodejs and browersify is for compiling for the browser :)

[jihoonl]

Ah Since we are releasing roslib.js in build directory which include everything, I thought we should not release src directory in npm. They are duplicated information.

Also users should be able to use roslib like the following rather than digging through src directory.

var Ros = require('roslib').Ros;

To keep the similar use pattern as browser version introduced in our example

It was the reason main field points to build directory.

But I can see your point that it would break browserify process. Could we find a way to release just a built version(in build directory) without exposing src and not break browserify process?

If there is no alternate way, yeah we should include src in release package.

[megawac]

You only need to include the license and build files (see underscore.js)

We use various shims to mock things like browser compliant xml parsers for node. Not exposing the src directory would require a seperate nodejs build to include support for canvas, websockets, tcp connections, and various other stuff that isn't included in the browserified build.

[megawac]

Also, in regards to browserify usage of the src directory, exposing src allows people to make slimmer builds excluding things like tf client or math if they don't need them

[megawac]

Also users should be able to use roslib like the following rather than digging through src directory.
var Ros = require('roslib').Ros;

They can do that currently, leaving main: "src/roslibnode".

[jihoonl]

Ah.. maybe I am misunderstanding something. Could we gchat quickly?

[jihoonl]

After chatting with @megawac, it becomes clear to release src rather than build. PR will get updated.

[megawac]

This still has to be removed

[rctoris]

👍 Thanks for taking lead on this @jihoonl , you know much more of the node side than I!

[jihoonl]

ready to go! merging and releasing.