vuejs
Firefox addon still on version 6
I am not sure if you also maintain the firefox addon page (https://addons.mozilla.org/en-US/firefox/addon/vue-js-devtools/), but the devtools are still at version 6.6.3 in the Mozilla Add-Ons directory. In the docs it says that "We'll launch on the Firefox App Store once v7.x is stable.", but 7 seems to be stable for a few months already. It would be great if you could update the Firefox AddOn, so that Firefox and Zen users can also get the best Vue experience.
We just released v7 stable version on the Google Store, and when we stabilize it here, we'll update the Firefox extension to v7 simultaneously.
We just released v7 stable version on the Google Store, and when we stabilize it here, we'll update the Firefox extension to v7 simultaneously.
Thanks for the quick reply, is there any roadmap or estimate for this? Just in terms of weeks or months.
Is there really something blocking publishing v7 for Firefox? Or it just wasn't published yet?
Could it be that v6 is not working with vue3? I don't see any components in Firefox...
Do you have any updates or timeline for when v7 of the Vue dev tools will be released on Firefox?
This is frustrating... Feels like this project stopped caring about Firefox at all 😢 (Or lost access to AMO...) There isn't even an out of store signed XPI to manually try v7, short of side loading in development mode...
@alexzhang1030 @webfansplz maybe you mates need some help with Firefox support?
I can report that the self built FF extension is working fine for me. Unfortunately, it is unnecessarily hard to self build, because of a faulty manifest.json. Instead of maintaining a fork, I've build myself a small script to build the latest version:
#!/bin/sh
cd packages/firefox-extension
git checkout manifest.json
cat manifest.json | jq --argjson browser_specific_settings '{"gecko": {"id": "[email protected]", "strict_min_version": "58.0"}}' '. + {browser_specific_settings: $browser_specific_settings}' > tmp.json
mv tmp.json manifest.json
zip -1 -r ../../vue-devtools.xpi * --exclude 'node_modules/*'
git checkout manifest.json
Place this in the repository root and run it to get a vue-devtools.xpi that you can install locally. Of course, updates are fully manual (pull latest code, rebuild, install in FF) this way.
So yeah, I would also appreciate a prebuilt official extension for FF very much.
I would also like to see an update for firefox ☝ With Pinia's latest update it doesn't show up in the devtool anymore.
Thanks for all your feedback. Devtools now supports Firefox extensions, and I will discuss the Firefox extension store ship plan with Evan.
I can report that the self built FF extension is working fine for me. Unfortunately, it is unnecessarily hard to self build, because of a faulty manifest.json. Instead of maintaining a fork, I've build myself a small script to build the latest version:
#!/bin/sh cd packages/firefox-extension git checkout manifest.json cat manifest.json | jq --argjson browser_specific_settings '{"gecko": {"id": "[email protected]", "strict_min_version": "58.0"}}' '. + {browser_specific_settings: $browser_specific_settings}' > tmp.json mv tmp.json manifest.json zip -1 -r ../../vue-devtools.xpi * --exclude 'node_modules/*' git checkout manifest.jsonPlace this in the repository root and run it to get a
vue-devtools.xpithat you can install locally. Of course, updates are fully manual (pull latest code, rebuild, install in FF) this way.So yeah, I would also appreciate a prebuilt official extension for FF very much.
I also has to remove the "version_name" key from the manifest.json in order to install it successfully. But unfortunately, once I installed the extension, it didn't work (Vue.js not detected)...
@Joulss I'm sorry it does not work for you. Did you try an official build of the extension for Chrome to make sure it's not your app setup?
App setup instructions are here: https://devtools.vuejs.org/guide/vite-plugin#usage
All I can say is Vue.js detection is working flawlessly for me across multiple (Vue 3) apps.
Thanks for all your feedback. Devtools now supports Firefox extensions, and I will discuss the Firefox extension store ship plan with Evan.
Any news?
Thanks for all your feedback. Devtools now supports Firefox extensions, and I will discuss the Firefox extension store ship plan with Evan.
@webfansplz Any news? When will the update be uploaded?
For users who are blocked, you can try it out as a workaround, and we'll publish it to the Firefox store soon.
For users who are blocked, you can try it out as a workaround, and we'll publish it to the Firefox store soon.
I get this error when loading the file. Firefox 137.0.2 (aarch64) edit: Same on 138.0 (aarch64)
I just checked this packaged extension, and the manifest needs the very same patches that I applied here: https://github.com/vuejs/devtools/issues/660#issuecomment-2670465344
Unzipping, fixing the manifest and re-zipping fixes it, otherwise, you will get the error message as posted by @bperel .
I just checked this packaged extension, and the manifest needs the very same patches that I applied here: #660 (comment)
Unzipping, fixing the manifest and re-zipping fixes it, otherwise, you will get the error message as posted by @bperel .
Thanks! I adapted your script to apply the JSON patch to the ZIP:
TEMP_DIR=$(mktemp -d)
ZIP_PATH="$(pwd)/devtools-firefox.zip"
unzip -p "$ZIP_PATH" manifest.json | jq --argjson browser_specific_settings '{"gecko": {"id": "[email protected]", "strict_min_version": "58.0"}}' '. + {browser_specific_settings: $browser_specific_settings}' >"$TEMP_DIR/manifest.json"
cd "$TEMP_DIR"
zip -u "$ZIP_PATH" manifest.json
cd ..
rm -rf "$TEMP_DIR"
For Windows users who didn’t understand the scripts — Here’s a ready-made manifest.json. Just replace the existing one in the downloaded archive with this file. Then go to about:debugging#/runtime/this-firefox and load the archive using "Load Temporary Add-on". At least for me, everything worked fine on Firefox version 138.0.
I also tried to write a PowerShell script, but unfortunately, I couldn’t get it to work. Maybe someone here with more experience can figure out what’s wrong — if it’s even needed at all.
$tempDir = New-Item -ItemType Directory -Path ([System.IO.Path]::GetTempPath() + [System.Guid]::NewGuid().ToString())
$zipPath = Join-Path (Get-Location) "devtools-firefox.zip"
$manifestJsonPath = Join-Path $tempDir "manifest.json"
# Извлечь manifest.json из ZIP
Add-Type -AssemblyName System.IO.Compression.FileSystem
[System.IO.Compression.ZipFile]::ExtractToDirectory($zipPath, $tempDir)
# Обновить manifest.json с помощью jq (нужно установить jq)
Get-Content "$manifestJsonPath" | jq --argjson browser_specific_settings '{"gecko": {"id": "[email protected]", "strict_min_version": "58.0"}}' '. + {browser_specific_settings: $browser_specific_settings}' | Set-Content "$manifestJsonPath"
# Обновить zip
Add-Type -AssemblyName System.IO.Compression.FileSystem
$zipArchive = [System.IO.Compression.ZipFile]::Open($zipPath, 'Update')
$entry = $zipArchive.GetEntry("manifest.json")
if ($entry) {
$entry.Delete()
}
[System.IO.Compression.ZipFileExtensions]::CreateEntryFromFile($zipArchive, "$manifestJsonPath", "manifest.json")
$zipArchive.Dispose()
# Удалить временную папку
Remove-Item -Recurse -Force $tempDir
For users who are blocked, you can try it out as a workaround, and we'll publish it to the Firefox store soon.
@bperel @ralph @SWDevStudio Thanks for the feedback, I've updated the package, try it out.
Thanks! I can confirm that the latest version provided by you installs flawlessly in my FF.
Thanks for taking care of the Firefox plugin @webfansplz ! It’s important to have an alternative to Googles web monopoly.
Thanks for all your feedback. Devtools now supports Firefox extensions, and I will discuss the Firefox extension store ship plan with Evan.感谢您的所有反馈。Devtools 现在支持 Firefox 扩展，我将与 Evan 讨论 Firefox 扩展商店的交付计划。
Any news? When will the update be uploaded? What can I help? Thank you.
Guys, if you need any help with the extension to publish it to the store, please let us know — we're really looking forward to it :)
For users who are blocked, you can try it out as a workaround, and we'll publish it to the Firefox store soon.
Any updated? ^_^
