microsoft / microsoft/azurechat
(x) Failed: Packaging service frontend
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
azd up commend not working.. I'm getting this error..
(x) Failed: Packaging service frontend
ERROR: error executing step command 'package --all': failed restoring service 'frontend': failed to install project /Users/juliejulie/ERA/src: exit code: 190, stdout: , stderr: npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /Users/juliejulie/ERA/src/node_modules/eslint-import-resolver-node
npm ERR! dest /Users/juliejulie/ERA/src/node_modules/.eslint-import-resolver-node-eFNhXYmm
npm ERR! errno -66
npm ERR! ENOTEMPTY: directory not empty, rename '/Users/juliejulie/ERA/src/node_modules/eslint-import-resolver-node' -> '/Users/juliejulie/ERA/src/node_modules/.eslint-import-resolver-node-eFNhXYmm'
npm ERR! A complete log of this run can be found in: /Users/juliejulie/.npm/_logs/2024-06-06T22_02_38_610Z-debug-0.log
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.
Research direction
Start by reproducing azd up for the frontend service and inspect the package --all step and the npm ENOTEMPTY log for eslint-import-resolver-node. Done means frontend packaging completes without the service restore failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, nodejs, typescript
- Domain
- build-system, cloud, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100