Debugging fails with ENOENT when running JavaScript + AZD templates with package.json under src
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, javascript
Research direction
Start by reading the linked vscode-azurefunctions issue and the solution described in the linked quickstart PR comment. Reproduce debugging with a JavaScript AZD template whose package.json is under src, then trace the ENOENT path failure. Done means debugging starts successfully without ENOENT.
Written by the indexing model from the issue text.
Description
See: https://github.com/microsoft/vscode-azurefunctions/issues/5128
I commented on the PR where this issue was introduced with a solution: https://github.com/Azure-Samples/functions-quickstart-javascript-azd-timer/pull/3#issuecomment-4918054709
- Dominant language
- Bicep
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100