[RFC] Initialize a Plasmo project from an existing extension manifest

[louisgv]

How do you envision this feature/change to look/work like?

• pnpm create plasmo OR pnpm dlx plasmo init OR plasmo init inside a directory with a manifest.json file
• plasmo takes the manifest and determine if it's MV2 or MV3.
  • If MV3, it keeps the basic structure and convert most of the config into the package.json
  • If MV2, it convert the manifest into mv3 and throw them into package.json as much as possible, and provides guideline on how to migrate their project from there.

What is the purpose of this change/feature? Why?

• It welcomes existing extension to convert over into Plasmo
• It leads to a future of code as config and automated configuration, rather than static json blob. This allows seamless transition to a future MV4 in the next 10 year
• It will ease the transition for existing mv2 extension over into mv3, and eventually to future mv4 or whatever. The framework will handles the transition for them while keeping their build target afloat, allowing developer to just focus on their product.

(OPTIONAL) Example implementations

No response

(OPTIONAL) Contact Details

No response

Verify canary release

• I verified that the issue exists in plasmo canary release

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.

[louisgv]

Would be cool if we can convert all the extension in https://github.com/mdn/webextensions-examples into plasmo, effectively solving mdn/webextensions-examples#496