[RFC] Supports jsx file extensions

[pd4d10]

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

Currently, background.ts, content.tsx and popup.tsx are the name conventions to create different type of pages. It would be great to also support background.js, content.js and popup.js.

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

To support dev languages other than TypeScript, for example Flow or ReScript

(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]

Thanks for the RFC! Would you like to spearhead this initiative? @pd4d10

[pd4d10]

Sure, I'll try to look into it

[louisgv]

A couple challenges on top of my mind:

• We will need to make sure the file extension auto-resolver for each ui library can recognize js files
• We need to handle .js extension file generation. If we can be smart about how we handle the file path, we can just pass the path directly into the import statement?

Technically... you can just use Rescript or Flow in a separate bundling process and import your files into an entry file within Plasmo. It's an extra build step but it will allow you to use js/whatever you like in your extension. The key part that need to be ts and tsx are really the entry files. Try it out - you can import .js file in those entry files.

[louisgv]

So a quick note from #363 - js extension doesn't work since we want to leverage the use UI libraries. jsx extension makes more sense since it indicate the use of template syntax.

For ReScript, see #367