Tag 1.0.0 and publish as an NPM package

[jankeromnes]

This allows getting the catalog like so:

$ npm install devices.json
$ node
> require('devices.json')

Ideally, we should also automate the S3 and NPM deployments of this catalog, e.g. on every Git tag with Travis CI like so.

[jankeromnes]

Publishing an NPM package, in addition to our CDN and GitHub deployments, responds to a user request on Twitter: https://twitter.com/alloy/status/1062645363499261952

[alloy]

Ace, thanks @jankeromnes! 🙏

For some context, I’d like to use this list to constrain the markup we render and send over the wire for those cases where we definitively know the screen sizes (and those are also the devices that could do with less bytes over the wire). Having this be a package that I can upgrade as part of our routine dependency upgrades and automatically get new device definitions for free would be great.

[martinbalfanz]

I like the suggestions, esp. automating the deployments to both S3 and NPM. Let's do this!

@alloy I just want to mention that this list is very specific to Firefox' RDM. Therefore, we may add/remove/modify devices on an irregular basis. Also, with our investment into mobile browsers, we will modify the user agents to match Firefox where possible. It seems irrelevant for your use case, but I thought to make you aware 🙂

[alloy]

Ohhh, that’s a good FYI, thanks, because that’s not what I need 😞 I think I’ll have to maintain our own database of user-agent to device size mappings (or regular-expressions to max sizes, eg in case of iPhones which don’t include model info in user-agent).

@jankeromnes Sorry for not realising this earlier, but thanks so much for wanting to assist! 🙏 I hope your effort wasn't for nothing.