Josh Smith

Just an update to @jackhair's comment here that you should be able to use version `0.4.0` and up now rather than pull from `master`.

@caltabid thanks for the PR! Are there any issues with the recent merges here? Would you mind rebasing and checking? Thank you!

@Jordan4jc here's an example used in a production application, if it helps: https://github.com/code-corps/code-corps-ember/blob/4d93edcef0d46592f5359f0c45939d55c24ca6bd/app/templates/components/donation/donation-container.hbs#L15-L31

And actually, the _really_ relevant stuff is found here: https://github.com/code-corps/code-corps-ember/blob/develop/app/controllers/project/checkout.js#L36-L46

In particular, you want to notice doing something like this: ``` async _createStripeToken(stripeElement) { let stripe = get(this, 'stripev3'); return await stripe.createToken(stripeElement).then(({ error, token }) => { if (error) {...

This is also complicated by the story around Service Workers and Firefox's Event Pages: > In Firefox, we have decided to support Event Pages in MV3, and our developer preview...

Here's an approach we could take with this: - Create different manifest versions in `src` - `src/manifest.v3.json` and `src/manifest.v2.json` - OR `src/manifest.BROWSER.json` – `src/manifest.chrome.json`, `src/manifest.firefox.json`, etc - Add a step...

- https://github.com/abhijithvijayan/wext-manifest-loader > Generate browser tailored manifest.json for Web Extensions that you specify properties to appear only in specific browsers.

Another approach would be to use [CopyWebpackPlugin](https://webpack.js.org/plugins/copy-webpack-plugin/) or similar to copy the files individually depending upon the browser target.

A `/src/manifest.json` using `wext-manifest-loader` would look something like this: ```json { "manifest_version": 2, "__chrome__manifest_version": 3, "name": "Chrome Extension Starter", "description": "A Chrome Extension starter kit", "version": "1.0.0", "browser_action": { "default_icon":...