materialdesignweb VS material

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

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.

I want to use ionic with material design. I am stuck between using ionic directives with custom CSS and angular-material

Angular Material

Okay, so take this with a grain of salt, because I have never made an NPM package and only work with recent versions of angular ... But looking at Angular Material's dev dependencies, they start at "angular": "^1.8.2", so I have a feeling you could do something similar in your package.json. The ^ symbol means "this version or higher".

Github Stars: 20,000+ Weekly npm downloads: 480,000+ Latest update: 8.0.1