Conversation
|
Thanks @TimKam. Would you suggest to split the JS/C++ part into two separate got repos? |
|
Ah, ok. If I understand it correctly now, the JS library is compiled from a C++ source. Then I recommend to just clean up the repo and docs a bit, to make it easier to understand what is source, what is build, and what are examples, and to add some documentation on how to work with the npm module. I can try to find the time and help. |
|
Here's how to publish npm packages. I was not entirely correct about package signing, as npm does apparently sign packages since a couple of months. |
* Add instructions on how to work with the JS lib via npm (once published) * Re-structure repo to allow for a clearer overview * Update docker files accordingly * Add Node.js client example, with tutorial * Update documentation according to changes
|
@chrberger, here's a comprehensive update:
Before the changes are merged, it would make sense to first check out this branch and publish libcluon.js on npm, or to publish immediately after merging. Also, I did not create a docker image for the npm client, which might be a nice addition. |
|
@TimKam Great, thanks. I will pull the branch and test it locally. |
Just an example: package.json for npm. Should be technically sufficient to publish, but adjusting the docs and repo structure would be good.