materialdesignweb VS cordova-plugin-health

I wanted something that didn't require recompilation and allows me to extend built components. Like an Chip extends a Button. I needed something that allows modification of its HTML template and layering of CSS styles on top of an extended element's styles. Frameworks are pretty rigid in this regard and I wanted to write less code to make a smaller final deployment, instead of copy pasting or having to write complicated mixins and abstractions.

My phone is basically grayscale expect for really minor blue hue. I'm not sure why, and I know how the Material You theming works (built a framework around it).

For the curious: Test page - Source Code

Source: https://github.com/clshortfuse/materialdesignweb/tree/archive-md2/components

If you're tired of it, I've been maintaining my MD framework for more than 4 and a half years since 2018. And before that I was working with Google on the AngularJS implementation in 2015. So I've been looking at and working on the same styles for over 7 years.

Here is the JS for one of the components. Only Chrome natively understands it right now. The alternative is to use a element referencing the CSS, but will call FOUC on the first fetch.

Code

It depends on the complexity of the API you are trying to access. So for example one of the plugins is called cordova-plugin-health. This plugin does native on-device queries against iOS HealthKit and Google Fit on Android. As you can see from the many many forks this plugin doesn't really translate the data 1:1 into JavaScript land. It essentially is only a subset of the whole API so when you want to access the real thing you're talking about forking the plugin and maintaining your own version. So you're right that small mods can be made but it's sorta like forking a jquery plugin. Now it's your problem.