In this post, I would like to explain how the service was shaped and how some of the decisions where made that come with creating a new product.
At the time when the original announcement was made, I was unsure which features would be most useful, so I made a survey. 56 people where kind enough to answer the questions. If you where one of them, thank you so much — you helped me a lot!
I was asked to publish the results of the survey, so let’s start with the question with the most surprising result:
My expectation was that GitHub pull request and npm hook integrations would receive the most votes. Talking to potential clients emphasized that they’d prefer to make on-demand calls from a developers workstation. This lead to a pivot and the focus was shifted to make the command line tool the main interface of the service. This also allows for easy CI integrations.
I’m happy to announce that
@studio/cli v1.0 is now available as an open source project on GitHub.
Would you use one of these features?
I was expecting the automatic API documentation to be interesting since discoverability of APIs can be a pain point when learning a new code base. However, I completely dropped this feature for now. It might be added back in at a later time, but currently all development efforts go into the runtime error detection.
How do you feel about uploading PRIVATE project sources?
I was also asked to offer an On-Premises version of the tool. If you are interested in this, please get in touch.
Which language level do you use mostly?
The answers to this question were no surprise. However, the analyzer is still not able to work on ES 6 sources directly. This is going to be the #1 priority going forward. For now, you can use Babel to translate your sources into ES 5, as described in the documentation.
Which environments do you write code for?
Interestingly, there is close to no difference between Node.js and Browsers here. The current state is that the service evaluates the code in a browser-like environment, because for Node.js support, ES6 is a precondition.
How about open source projects?
Paid subscription plan
If you exceeded the credits in the free tier, you can subscribe to the “Developer” plan for $9.90 per month. If you want to support the project, please consider subscribing right away!
Get in touch!
Thank you for reading!