Does Plasmo support Vue HMR for Content scripts?
Tilde Import for `.mjs`
.ts to .mjs and I noticed that it's now unable to be imported via ~config/env.mjs (located in /src/config/env.mjs). It used to work when it was a .ts file. I think it's due to this: https://docs.plasmo.com/framework/import#tilde- Any reason .js and .mjs aren't a part of this?How to make tab pages with vue?
How to use shadcn-ui stylings in content script?
MUI select components don't inherit styling
Extension fails to run due to Parcel - The Expression evaluated to a falsy value
CSUI main world on Firefox MV2 (Unexpected property "world" for scripting.registerContentScripts)
plasmo dev --target=chrome-mv3, but it's not working for plasmo dev --target=firefox-mv2 (no CSUI shows up on the page). is injecting to the main world supported for mv2? if not, are there any alternative ways to execute a pre-existing function from the main world and return the data to the CSUI? thanks!
the error in devtools is: Uncaught Error: Type error for parameter scripts (Error processing 0: Unexpected property "world") for scripting.registerContentScripts. (screenshot attached)
possibly relevant project information:...Render content UI on specific URL in SPA
Injecting both Emotion cache AND local css
Typescript unions not working

Why do I keep getting the errors of `Uncaught Error: Extension context invalidated.` and `React.jsx`

Messaging between two content scripts
Losing styles when injecting popup component in CSUI

Import a custom package styling (React-hot-toast)
Anyone got devtools working with a React front end?
Multiple Content Scripts on One Page Not Working As Expected

Fails to load source maps
.plasmo/, didn't help
I'm on Edge on Windows 10...
Plasmo adds <all_urls> content script automatically, triggering host permissions
contents directory with some content scripts, however the generated manifest.json also adds an additional content script:
{ "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },
{ "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },
Using NextJS API routes works in dev but not in prod
/src/pages/api
And I can call them by making an "internal API call" from the client GET $PLASMO_PUBLIC_NEXT_URL/api/something...