Reading through some of these comments I agree: It is probably a good idea to add in a 'why to use' section on the repo. The purpose behind this was that I fou

Reading through some of these comments I agree: It is probably a good idea to add in a 'why to use' section on the repo. The purpose behind this was that I found it cumbersome to work with dataets in JavaScript so this framework lets you pull them into a schema that has metadata to handle relationships between tables, aggregation methods, sorting and filtering. As for competing frameworks: I have seen some of this in other larger frameworks but I build this out so I can work with data in JS without pulling in monolithic data visualization libraries.