Support browserconfig.xml

[YoranBrondsema]

Generates browserconfig.xml according to the spec on https://msdn.microsoft.com/en-us/library/dn320426(v=vs.85).aspx. This targets Windows machines. It only populates the <tile> property, not <badge> or <notification>.

It will need some refactoring first if PR #65 gets merged first.

[san650]

I've merged #65, can you update this PR to avoid using async/await in tests?

[YoranBrondsema]

@san650 Done! We can keep the async/await as that test is executed in the browser and transpiled with Babel. However, I did need to polyfill Array.prototype.includes in the Node.js addition to the addon.

[san650]

To keep backward compatibility it would be great if we make this file to be opt-in instead of opt-out. So we don't override browserconfig.xml on projects that already have one.

The idea would be that by default we don't generate it and when the ms configuration is truthy we would generate it, with ms: true or ms: { ... }

What do you think @YoranBrondsema ?

[san650]

Remove the reference to ms above (three lines above)

[YoranBrondsema]

Thanks!

[YoranBrondsema]

I agree! I'll make the changes.

[YoranBrondsema]

@san650 I made the changes. If the ms property is falsey, the browserconfig.xml and associated meta-tag won't be generated.

I added the ms property to the blueprint; let me know if you prefer to not have it there as well.

[san650]

Thanks for contributing this feature @YoranBrondsema !!!