There is inconsistent behaviour when working with boolean properties that map directly to an element's attribute. For example: $element->disabled = true should add the attribute disabled to the element, without a value. Subsequently, $element->disabled = false should remove the attribute. This is the same for selected, checked, etc.

• Step 1: List out all the boolean properties from a

first guide of capsid.js

• How to set up the dev environment. TypeScript + Parcel is the best choice.
  • We don't support non-TypeScript environment anymore because without typescript decorators, capsid doesn't make any sense.
• First step is create click handler
  • fetching items from click handler may be a good starting point.
• We should mention about lifecycle and initialization timin

Currently we run unit tests on the source code, but not integration in a browser environment on the generated file.

Tasks

• Research what kind of CI system we can use for free that hooks into GitHub, and what environments (OS/Browser) we can test in
• Research for an integration test system that works with Grunt and allows for multiple environments
• Build integration tests and Grunt ta

My suggestion is create a new topic in README with information about to how to execute the test. There is step for run to test, but this isn't documented.

var element = document.querySelector('.class-name');
var styles = styler(element).get(['height', 'width']); 

Should read

var element = document.querySelector('.class-name');
if (element) {
    var styles = styler(element).get(['height', 'width']); 
}

To prevent errors when running unit tests.