[BUG] How should I automatically translate the chrome api when building a firefox version?

[jeffminim]

What happened?

I want to try adapting firefox, but a lot of the API calls to browser I use chrome.*. However, when building --target=firefox, it looks like the plasmo framework doesn't translate automatically for me properly (chrome. -> browser.) Including, but not limited to, “chrome.runtime, chrome.storage, chrome.tabs, chrome.i18n”, which results in not work correctly in firefox.
Is there something I'm doing wrong? Or is this feature currently missing?

Version

Latest

What OS are you seeing the problem on?

Windows

What browsers are you seeing the problem on?

Firefox

Relevant log output

(OPTIONAL) Contribution

• I would like to fix this BUG via a PR

Code of Conduct

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

[muzammil0011]

Use webExtension-polifill instead

[spiceworm]

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API

Firefox also implements these APIs under the chrome namespace using callbacks. This allows code written for Chrome to run largely unchanged in Firefox for the APIs documented here.

Try to make minimal usage of direct calls to chrome.* APIs for things like chrome.storage and chrome.runtime.sendMessage and instead use plasmo APIs wherever possible.

https://docs.plasmo.com/framework/storage

https://docs.plasmo.com/framework/messaging