Migrate to caniuse-lite.

Hi @Nyalab!

I’ve been working on an unofficial way to consume caniuse support data that is intended for modules, whereas the official dataset is intended for people. So I dropped a lot of keys that Autoprefixer & Browserslist don’t use and then compacted the rest of the data. The end result weighs around 7 times less than the official database as of this writing, and the only downside is a slight performance hit when the data is restored into a caniuse format. We optimised for size, not speed, but I think we can perhaps improve this further in the future. For now the dataset is as close to caniuse-db as possible, for easy migration.

• https://travis-ci.org/postcss/autoprefixer/jobs/219404429 - caniuse-db
• https://travis-ci.org/postcss/autoprefixer/jobs/220033486 - caniuse-lite

So I think it’s important to use a single source of truth for the support data, and as I am starting to make much more use of caniuse-api I’d like to update the module to use caniuse-lite too.

My only reservation about the migration is that you are using the title key from each feature. I’d like to know if that can be dropped so that we can keep caniuse-lite as lean as possible. But I would like some input from caniuse-api users, on whether they think this is necessary or not. I’m open to any feedback! 😄

Copying in users of this module/caniuse data: @agauniyal, @una, @schiehll, @sylvainpolletvillard, @moox, @bebraw & @ai.

Thanks!

[MoOx]

What about letting people choose between one or the other? Anyway, node_modules for real world projet is never less than 100MB so not sure it’s super important.

[ai]

I think caniuse-lite is one of the best thing in frontend in 2017. With it we will dramatically reduce node_modules size around the world. Autoprefixer and Browserslist will use it in next major release.