Why is this not the same as "npm install sockjs-client"?

[statico]

It took me a while to understand that "npm install sockjs-client" does not install this module but installs https://github.com/sockjs/sockjs-client-node instead. That's really weird.

Would you mind clarifying this in the documentation?

[3rd-Eden]

It's even weirder that the module in node has a completely different api

[3rd-Eden]

FYI: I build https://github.com/3rd-Eden/sockjs-client-node which supports exactly the same API in node and uses the exact same codebase.

[piranna]

I'm more upset about why this project is marked as "private" on package.json. Anyway, there would be too much problem that "npm install sockjs-client" point to another project if at least it wasn't two years old... :-/

[humanchimp]

FYI, there is also my fork, which has the same API as sockjs client, but for node: https://github.com/humanchimp/node-sockjs-client

[piranna]

@humanchimp, have you tested if it's your fork still compatible with browser using browserify, maybe directly or by a 'browser' field? If so I would be interested on use it :-)

[humanchimp]

@piranna Yes, this is the reason for it. I needed to be able to use it as a drop in replacement for the client side SockJS library. As you suggest, you can use the "browser" field in your package.json to create the mapping. I'm still using the non-browserified library on the client side, so I'm using the browserify-shim transform in order to map require('sockjs') to the global SockJS object for the browser, and to my library in node. If you're using the browserified version, i guess that you don't need browserify-shim. I'll try to improve the README in this area.

[3rd-Eden]

@piranna Just because it uses browserify now it doesn't mean that the API has changed. It only changed the way source code has been build. All other node clients like I and @humanchimp has build would still work.

[piranna]

The problem is mainly that in our work flow at my job we generate a Node.js version and later a browser version from the same base code, so we try that the libraries are compatibles in both environments, and also that all of them are available on NPM to don't need to have bundled libraries.

[humanchimp]

OK, thanks for the clarification. No, my fork won't run in the browser. It's purpose is the reverse: take code that was meant to run in the browser originally, and run it in node without (much) modification. Once this sockjs project is published to npm, you can use my fork and the "browser" field in order to accomplish what you want, but since (AFAIK) this module is not currently published to npm, you'll need to use something like browserify-shim in order to map calls to require('node-sockjs-client') over to the global SockJS (and you will need to ship that file independently of the browserify bundle.) I hope that this sockjs client will be published to npm soon, but it seems like the build is failing for now.

[brycekahle]

Duplicate of #76

[brycekahle]

Heads up that 1.0.0-beta.4 has been published to npm, and all future versions will be too.