Skip to content
loading...

Looking for good practices for JS SDK

obstschale profile image Hans-Helge Buerger github logo ・1 min read

I have built an online service with Laravel*, which has a REST API to interact with. Now I'm going to build a CLI tool to send data to the service using JS. I'm fairly new to CLI tools with JS. For this CLI tool I want to write a separated SDK so others can use it as well.

What are good / best practices to write an REST SDK in JavaScript? Do you have some advice for me or do you know a good SDK I can dig into?

I appreciate your help!

* it's called Speedtest Collector if you're interested.

twitter logo DISCUSS (6)
Discussion
markdown guide
 

Thx. That looks promising. I will take a deeper look in the next days.

Kind of. Depends on you if its interessting ;)

You probably know speedtest.net or other speedtest sites. I work on a service, which saves the speedtest and displays graphs and statistics for your internet connection. The service is called Speedtest Collector.

To make it easier for the user, I work on a JS CLI tool to make speedtests and send them directly to my service. Therefore, I want to create an SDK to dogfeed it in my CLI tool.

If you're interested, you can sign up for the newsletter and I send you an eMail whenever its ready.

 

It seems there are not good practices for JS SDKs. ¯_(ツ)_/¯

Classic DEV Post from Jul 30 '19

PublishTo.Dev: Scheduling article publishing on dev.to

Hans-Helge Buerger profile image