What problem does this feature solve?

I'm a developer working on a browser extension that uses Vue.js. I'm currently working on porting my extension over to Firefox. Mozilla has an automated validation process that determines whether or not your extension requires manual review before the extension is released to users.

One issue I'm running into is that the Vue runtime bundle includes assignment to innerHTML (src), which generates this warning:

From what I can tell from the code comment and the PR where this logic was added, it's only there for IE11 support.

It would be nice if there were a way for us to opt-out of this behavior since our browser extension doesn't support IE11. What I mean by "opt-out" is that the innerHTML assignment would not be included in the vue-cli-service build output.

What does the proposed API look like?

Ideally, this switch could be based on the browsers we have configured in our .browserslistrc. We currently only support the last 5 versions of Firefox and Chrome, so we don't need any IE11 fallbacks. Though, I'm not sure if any introspection/updating of the Vue distfiles are done at build-time, so that might be a challenge.