AutolabJS/AutolabJS

## Description
 - Describe proposed changes in detail here. Make a bullet list if multiple relevant changes are present
 - However, it is not advisable to combine irrelevant changes into one pull request. Create a separate pull request for each proposed change.

## Motivation
 - Why is this change required? What problem does it solve?
 - If it fixes an open issue, please link to the issue here, and in the commit message.

 ## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

## Checks
 - [ ] Squash your commits down to one, or a few, discreet changesets before submitting a pull request
 - [ ] Read the [contributing guide](https://github.com/AutolabJS/AutolabJS/blob/master/CONTRIBUTING.md)
 - [ ] PR should be motivated, i.e. what does it fix, why, and if relevant how
 - [ ] If possible, include an example in the description, that could help all readers (including project members) to get a better picture of the change
 - [ ] Avoid other runtime dependencies unless abslutely necessary
 - [ ] Rebase your commit history so that each commit is meaningful and states the intention behind the change
 - [ ] Ensure that your pull request follows the [style guidelines](https://github.com/AutolabJS/AutolabJS/wiki/Coding-Standards)
 - [ ] At least one commit should mention `Fixes #<issue number>` _if relevant_

## Notify reviewers
@prasadtalasila