adobe / adobe/aio-cli-plugin-runtime
Unable to debug runtime action from vscode because of invalid .vscode/launch.json
- Dominant language
- JavaScript
- Stars
- 21
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Unable to debug runtime action from vscode because of invalid '.vscode/launch.json' (similar to #244)
The generated .vscode/launch.json look like this (**note the wrong envFile property**).
```
{
"configurations": [
{
"type": "pwa-node",
"name": "Action:wknd-spa-react-0.1.0/ssr",
"request": "launch",
"runtimeExecutable": "${workspaceFolder}/node_modules/.bin/wskdebug",
"envFile": "${workspaceFolder}//Users/johndoe/Downloads/aem-guides-wknd-spa.react.ssr/ui.frontend/dist/application/.env.local",
"timeout": 30000,
"killBehavior": "polite",
"localRoot": "${workspaceFolder}",
"remoteRoot": "/code",
"outputCapture": "std",
"attachSimplePort": 0,
"runtimeArgs": [
"wknd-spa-react-0.1.0/ssr",
"${workspaceFolder}/actions/ssr/index.js",
"-v",
"--disable-concurrency",
"--kind",
"nodejs:10"
]
}
],
"compounds": [
{
"name": "Actions",
"configurations": [
"Action:wknd-spa-react-0.1.0/ssr"
]
}
]
}
```
**To Reproduce**
Steps to reproduce the behavior:
1. Create an AEM Project using [AEM Project Archetype](https://github.com/adobe/aem-project-archetype) with SSR enabled
2. Follow the instructions in `ui.frontend/README.md` to debug AEM SSR via local Docker image of OpenWhisk
3. Run `npm run build-with-ssr`
4. Run `npm run start-ssr-ioruntime`
5. Attach the debugger via provided VS Code Launch configuration and observe the Debug Console
**Expected behavior**
Debugger attaches without any errors.
**Screenshots**
**Desktop (please complete the following information):**
- OS: macOS Ventura 13.4
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start with the generated .vscode/launch.json and the SSR debugging instructions in ui.frontend/README.md. Reproduce the issue with npm run build-with-ssr and npm run start-ssr-ioruntime, then trace how the VS Code launch configuration is generated. Done means the generated envFile path is valid and the debugger attaches without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100