[Help] Couldn't find the Firefox executable. Please correct the path given in your launch configuration.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Stack tecnológico
- typescript, vscode
- Área
- developer-experience, tooling
Línea de trabajo
Empieza con las configuraciones launch.json indicadas y el ajuste de VS Code firefox.executable, y después reproduce el fallo de Run and Debug usando la ruta de Firefox Developer Edition en Windows. Se considera terminado cuando la extensión acepta el ejecutable configurado e inicia Firefox o se conecta a Firefox sin el error indicado.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Overview of the Problem
I can't get RUN AND DEBUG to work. It says it can't find my firefox executable:
launch.json Changes
I've changed my launch.json to include "firefoxExecutable": "C:\\Program Files\\Firefox Developer Edition\\firefox.exe" in all configurations.
launch.json Content
{
// Firefox debug configurations for the "Debugger for Firefox" extension
// (firefox-devtools.vscode-firefox-debug).
//
// Pick a configuration from the Run and Debug dropdown, then press F5.
//
// - "Firefox: Current file (file://)" -> debug whatever HTML file is
// currently active in the editor
// - "Firefox: Main test page (file://)" -> debug Chromatic Pro Var.html
// regardless of which file is active
// - "Firefox: Current file via localhost" -> serve the workspace over HTTP
// (npx serve) and debug the active
// HTML file at http://localhost:5500
// - "Firefox: Attach to running Firefox" -> attach to a Firefox instance you
// started yourself with remote
// debugging enabled (port 6000)
"version": "0.2.0",
"configurations": [
{
"name": "Firefox: Current file (file://)",
"type": "firefox",
"request": "launch",
"reAttach": true,
"file": "${file}",
"pathMappings": [
{
"url": "file://${workspaceFolder}",
"path": "${workspaceFolder}"
}
],
"keepProfileChanges": true,
"log": {
"fileName": "${workspaceFolder}/.vscode/firefox-debug.log",
"fileLevel": {
"default": "Warn"
}
},
"firefoxExecutable": "C:\\Program Files\\Firefox Developer Edition\\firefox.exe"
},
{
"name": "Firefox: Main test page (file://)",
"type": "firefox",
"request": "launch",
"reAttach": true,
"file": "${workspaceFolder}/Chromatic Pro Var.html",
"pathMappings": [
{
"url": "file://${workspaceFolder}",
"path": "${workspaceFolder}"
}
],
"keepProfileChanges": true,
"firefoxExecutable": "C:\\Program Files\\Firefox Developer Edition\\firefox.exe"
},
{
"name": "Firefox: Current file via localhost",
"type": "firefox",
"request": "launch",
"reAttach": true,
"url": "http://localhost:5500/${fileBasename}",
"webRoot": "${workspaceFolder}",
"preLaunchTask": "serve workspace on :5500",
"postDebugTask": "stop server",
"keepProfileChanges": true,
"firefoxExecutable": "C:\\Program Files\\Firefox Developer Edition\\firefox.exe"
},
{
"name": "Firefox: Attach to running Firefox",
"type": "firefox",
"request": "attach",
"port": 6000,
"host": "localhost",
"firefoxExecutable": "C:\\Program Files\\Firefox Developer Edition\\firefox.exe",
"pathMappings": [
{
"url": "file://${workspaceFolder}",
"path": "${workspaceFolder}"
},
{
"url": "http://localhost:5500",
"path": "${workspaceFolder}"
}
]
}
]
}
VS Code Settings Changes
I've changed the following VS Code settings to point to my Firefox path:
firefox.executable("C:\Program Files\Firefox Developer Edition\firefox.exe")workbench.externalBrowser("C:\Program Files\Firefox Developer Edition\firefox.exe")
All of the "firefoxExecutable" entries are correct. My system's Firefox installation is at C:\Program Files\Firefox Developer Edition\firefox.exe.
Firefox about:config Changes
I changed the following values in about:config in FF:
devtools.debugger.remote-enabledtotruedevtools.chrome.enabledtotrue
Help Request
After all of these edits, I still cannot debug from the "RUN AND DEBUG" window. Still getting the Couldn't find the Firefox executable. Please correct the path given in your launch configuration. error.
Can someone explain to me the correct way to configure this plugin so I can debug with FF Dev Edition?
I have no clue why it's not working.
Thank you in advance for any help at all.
- Lenguaje dominante
- TypeScript
- Estrellas
- 447
- Forks
- 76
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firefox-devtools/vscode-firefox-debug
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
firefox-devtools/vscode-firefox-debug#391 · 2 comentarios · 1 reacción ·
-
bug path mapping
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
CastleAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
-
Create new issueAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 1/100
-
Asus Snapdragon win11 installAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
firefox-devtools/vscode-firefox-debug#390 · 1 comentario ·
Todos los issues de firefox-devtools/vscode-firefox-debug
Issues similares
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
inu-appcenter/memorIN-frontend#106 ·
Los mantenedores suelen responder en 1 día
-
kind/bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 7 días
-
[Bug] @deck.gl/arcgis dist import resolves to unpublished @deck.gl/core source path (9.3.11, 9.4.0)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
fix: CopyFilters ignores tabAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
CSCfi/sd-search-ui#145 ·
Los mantenedores suelen responder en 1 día
-
Add: Cbeebies pl SDAbiertocheck:passed streams:add
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día