A node.js api client

[laBecasse]

Hello everyone, I made a client for shaarli api in node.js: shaarli-api. I hope that some of you can test it ;)

[ArthurHoaro]

Hi! Thanks for the feedback, that's nice, I'll give a try later.

However, you only implemented 3 out of 7 endpoints, and let out the GET and PUT link methods which are kind of essential. :)

[laBecasse]

Yes it is just a begin, but I will add the two endpoints you mention pretty soon.

[laBecasse]

Now there are 6 of the 7 endpoints :smile:

[virtualtam]

Thanks @laBecasse ;-)

To avoid confusion, I'd suggest renaming:

• the project & node package to shaarli-client or shaarli-api-client
• the main class to ShaarliApiClient or ShaarliApiV1Client

[laBecasse]

Hep, I understand my mistake, but actually I just can't rename the npm module : https://www.gregjs.com/javascript/2016/how-to-rename-a-published-npm-module/

So I don't know what to do to keep all stuff coherent. Any idea ?

[virtualtam]

The linked article provides good advice, but this mostly applies to libraries/projects that people start using and rely on; I'm not familiar with NPM's internals, but you should be able to opt for one of the following:

• create a new project, delete the old one
• create a new project, mark the old one as deprecated and add a redirection notice

Deletion might be available from the NPM management interface, or you may have to contact a platform administrator / a mailing list to ask for its removal.

Nevertheless, you can still:

• edit the project's description to highlight it is an API client
• pick suitable class names for API usage

[laBecasse]

Ok, I think that the name is corrected in all places, now ;)

[virtualtam]

Cool! Thanks @laBecasse for updating the NPM library, I'll add it to the Shaarli documentation ;-)

[virtualtam]

Closing as the library has been added to the Shaarli docs :)