MDN is releasing a new version of their website, which uses React. It looks super cool and we should add support for it.

Ran a quick test locally and things seem to just work.

I was at a Slack event the other day and was thinking that the general idea behind this package could be used for a great Slack bot. But to actually use it as such, there needs to be a way to require and execute the script so that it doesn't log to the console, but instead returns the information.

That got me thinking, maybe it makes sense to separate the data fetch entirely from the console output.

ie: we scrape the page for all the relevant, unformatted information and build an object, and then we return that (promise of an) object directly for people to do as they please, or we pass it to a function that then constructs the output for the console. The default behavior when installed globally would remain logging to the console, but as a locally installed module it could be useful in other projects, such as a Slack bot.

It would of course require a good deal of refactoring, but do you think this is worth doing? Either way, I'm free this evening so unless I get tempted by bourbon, I'll see if I can make a quick prototype ;-)

We should publish v1.2.0 to npm. I would just look through the diff, make sure that linting is 👍 and publish it.

Since we only support JavaScript (the default) and CSS, I think we can do:

$ mdn background-image --css

Instead of

$ mdn background-image --language=css

We can of course introduce this change with backwards compat.