I’m having trouble loading a GLTF asset in my Firefox add-on production build. In my code, I’m trying to construct the URL for the asset using browser.runtime.getURL , but it seems that the fallback is always used, so the GLTF is fetched via a relative path (my dev setup) (e.g., https://SOMEWEBSITE.com/pets/Glub.gltf ) and returns a 404. (‘pets/Glub.gltf’ is the path in my dist)
I’m making a virtual pet add-on for fun 
.
I build my React application using Webpack. The build process compiles all my code into bundles that are output into a specific folder within the extension’s package.
In my application’s entry script, I expose a mounting function on the global object. This function is responsible for rendering the UI into a designated container element. During local development, when such a container is already present on the page, the app auto‑mounts. For production, an injection mechanism (triggered for example by a background process) dynamically creates the container and then calls the mount function to display the UI.
"web_accessible_resources": [
"pets/Glub.gltf",
]
Has anyone encountered a similar issue when accessing extension-packaged assets (GLTF in this case) via browser.runtime.getURL in production? Any insights on why the browser object might be missing at runtime, or suggestions on how to ensure it’s available so I can correctly resolve the asset URL?
