icon font only release

[akash1810]

Installing material-design-icons via bower, npm, jspm etc pulls down the svgs and other artefacts, which is pretty big (26.9MB). Can there be a release that includes just the icon fonts themselves?

Its possible to reference the google web font url but that creates an external dependancy.

[jossef]

Update 2018-10-27

The lack of updates + development support issues also bothered me. I've forked this repo, added support for scss, removed irrelevant files and updated the fonts with the latest straight from Google's CDN.

material-design-icons-iconfont contain only the relevant font files (excluding the many source svg files which cause congestion)

bower install material-design-icons-iconfont --save
npm install material-design-icons-iconfont --save

Check it out: material-design-icons-iconfont

[mribichich]

+1 the same in my case.

I dont know how you do it, but in our CI it takes forever (10 min aprox) to copy all the icons for every format from the cache to the bower_components directory every time it runs bower install.

Its over 36MB and 77.500 files.

Maybe every format could have its own repo.

[FezVrasta]

+1

[shyndman]

Reasonable request. I'll see if I can get this going for our next release.

[FezVrasta]

Ah yea it would be awesome :D

[FezVrasta]

Any news about this feature?

[r0b-]

+1

[gonzofish]

@jossef thanks for doing that as a stopgap.

[jamesminotte]

How do I install the app password for gmail I thought this was it sorry if u have to keep it in lamens terms but I am in awe of ur billance

[lukengda]

Any news?
I would need a bower font release that keeps up to date from the material design icons team. All the third party font releases with bower are not updated regular enough.

[tklepzig]

+1

[artimeg]

+1

[aastrouski]

+1

[ShadowManu]

+1

[gwicksted]

+1

[ghost]

+1

[tkarls]

+1

[ShadowManu]

3rd party package to solve ths 1 year isssue I guess?

[alensiljak]

And the size is not 26MB any more but 32 nowadays. Not extremely significant, of course, but still terribly slow when run via git.

[ddyrcz]

[vikshv]

+1

[FezVrasta]

Hey Google, can we close this issue since it looks like a "wontfix" to me?

You have something like 300 bazillions of dollars and you can't spend 1 hour on this thing? If you don't want to fix it, say it, so we can forget about it and move in a different direction.

[ShadowManu]

@FezVrasta the thing about open source is that it is open. So, as frustrating as it may be, you have to remember what open means. And that includes the good and bad. The good when google publishes the icons and the community, like @jossef, can help on what users want. The bad, when even maintainers can't help on what users want.

I only say this not because your last paragraph was nonconstructive, the thing I most dislike in open source discussions.

Anyway, I'm following this thread and I would also like to have an official statement about this issue. We can safely consider it 'wontfix' after a year and a half, I guess. @shyndman?

[FezVrasta]

I don't say that they have to fix this issue, but damn it, they are one of the biggest companies in the world, at least add a stupid label to the issue and close it!

[rmacklin]

Thanks for your package @jossef. It sped up our node module installation by a factor of ~4.5. Hopefully the official package can provide this eventually.

[agavazov]

+1
89 815 Files, 8 002 Folders :(

[ghost]

+5

[p3x-robot]

so such a small thing to do it :(

[alensiljak]

Having 50K unneeded files under source control was killing our team. Now we've removed the material icons from all our projects and went back to Font Awesome. Problem solved.

[jaguileram]

+1

[ChenArno]

+1

[browne0]

+1

[ciceropablo]

+1

[rogerluiz]

+1

[Robula]

+1

[michieldewilde]

+1

[florin05]

+1
We use version 2, maybe 3 is smaller
89,818 Files, 8,005 Folders
81.8 MB (85,827,584 bytes)

[krystof-k]

I've created similar fork as @jossef that contains just production SVGs so that you can create your own SVG sprites: cloudaper/material-design-icons. Hopefully someone will find that useful.

[RoelN]

We're gathering all feedback and suggestions regarding updating the npm package in a central issue: #1129 Please have a look and see if the package, as published in the way suggested there, would suit your needs.