Hi James,
On 22.03.20 22:07, James Lacey wrote:
> I had need to bundle the nodejs library with Webpack for usage in the
> browser. When I ran "npm i thrift" against my project, it actually added
> the js (i.e. non-node) library. As far as I can tell, there isn't another
> Thrift package on npm. I ended up cloning the git repository and adding a
> resolve alias to my webpack.config.js. It would make more sense to me for
> the npm package to be the nodejs library. The js library is much more
> limited in functionality than the nodejs version. It would also be the
> version you would expect if you were writing a node application. The js
> version could be used with bower or downloaded and included directly in a
> page via a script tag. Am I missing something or am I doing something wrong?
Did you get this sorted out by now? I'm not a core developer but I wanted to
bring up that we've invested quite a bit to improve the node.js thrift in the
browser recently. What you can now find in git master is an improved version
that has support for websockets (with highly superior speed, if you need)
and many more updates like consistency fixes between JS and Node.js and many
dependencies update. It works quite well for us.
Let me know if you have more questions or want to discuss this.
Cheers,
Mario
