Generating Manifest V2 extension by default

[MaxterBattle]

Google search terms

Describe the bug

My initial trial of this boilerplate generated a manifest v2 extension. These are now effectively obsolete. Reading the more extensive extend-chrome docs, I think it supports manifest v3; anyone trying to build their first extension will be confused by this boilerplate.

How do we reproduce?

npx create-react-crx
cd # to project sub-dir
npm install  
npm run dev

Expected behavior

An installable extension with minimal function

Actual behavior

The generated extension won't install due to the v3 manifest in the ./dist folder.

Screenshots

Please complete the following information:

• Library Version: [email protected]
• Operating System: Windows 11
• Browser: Brave 1.42.86 Chromium 104.0.5112.81 (Official Build) (64-bit)
• Node Version: V18.5.0

[BurtHarris]

@jacksteamdev : Thanks for your work on this, are you maintaining this repo, or is there some better boilerplate you can point me to?

I'd be happy to contribute some PRs if you want to keep updating this.

[jacksteamdev]

@BurtHarris Thanks for your kind messages. I've mostly moved on to developing CRXJS, a Vite plugin with all the features of this boilerplate, but adds true HMR. You can check it out at https://dev.to/jacksteamdev/create-a-vite-react-chrome-extension-in-90-seconds-3df7

[jacksteamdev]

@BurtHarris I'd happily merge some PRs if you'd like to contribute here!