[FYI] import.meta failing firefox submission check #178
Replies: 5 comments
-
hmm... is this like Mozilla's reviewer's decision not to have this directive in the final bundle? I wonder why |
Beta Was this translation helpful? Give feedback.
-
|
There's a linter that is blocking it. They run the submission through the linter automatically. There a Mozilla support thread on it where I guess a senior staff probably made a fix to allow the linter allow import.meta from a long time ago But the linter still rejected my code submission |
Beta Was this translation helpful? Give feedback.
-
|
This is a link of the issue on Mozillas Github |
Beta Was this translation helpful? Give feedback.
-
|
Another way to work around this IMO, is to use the |
Beta Was this translation helpful? Give feedback.
-
|
But I think we can close this for now as this is not a Plasmo issue per-se, but a good pre-cautious for folks publishing to Mozilla store |
Beta Was this translation helpful? Give feedback.
-
What happened?
A bug happened!
firefox submission fails if i import svg icons using
import "url:./../assets/some-icon.svg"firefox store throws an error when the extension is submitted.
the import line above results in
import.metainjected into bundled code for popup.tsx.I have solved this by including the svg relative path in manifest.json and then obtaining the url using
chrome.runtime.getUrl('./assets/some-icon.svg')in popup.tsx.
The bundled applications works fine (both dev and build). But firefox addons submission page will reject it.
Its not an issue now for me but thought you should know. Someone else might bang their head for a few hours if they run into this.
Cheers from JiffyReader. This is really an awesome project.
Version
Latest
What OS are you seeing the problem on?
Linux
What browsers are you seeing the problem on?
Firefox
Relevant log output
No response
(OPTIONAL) Contact Details
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions