microsoft / microsoft/Agent365-Samples
Getting error while executing "a365 deploy" on Node Devin Sample
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 108
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Description
Executed Below Command Successfully
a365 config init
a365 setup all
Getting below error while executing a365 deploy
PS C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent> a365 deploy
Azure CLI is using 64-bit Python (optimal)
Validating Azure Web App exists...
Confirmed Azure Web App 'devina365-webapp' exists
Starting multi-platform deployment...
[1/7] Detecting environment...
Detecting platform in: C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent
Detected Node.js project
Detected platform: NodeJs
[2/7] Getting appropriate builder for NodeJs environment...
[3/7] Validating NodeJs environment...
Validating Node.js environment...
Node.js version: v24.14.0
npm version: 11.9.0
[4/7] Building NodeJs application...
Building Node.js project...
Installing dependencies...
ERROR: Command failed with exit code -4082: npm error code EBUSY
npm error syscall rmdir
npm error path C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent\node_modules\fast-uri
npm error errno -4082
npm error EBUSY: resource busy or locked, rmdir 'C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent\node_modules\fast-uri'
npm error A complete log of this run can be found in: C:\Users\myusername\AppData\Local\npm-cache_logs\2026-03-05T07_36_48_830Z-debug-0.log
WARNING: Warnings/Errors:
npm error code EBUSY
npm error syscall rmdir
npm error path C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent\node_modules\fast-uri
npm error errno -4082
npm error EBUSY: resource busy or locked, rmdir 'C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent\node_modules\fast-uri'
npm error A complete log of this run can be found in: C:\Users\myusername\AppData\Local\npm-cache_logs\2026-03-05T07_36_48_830Z-debug-0.log
WARNING: npm ci failed, trying npm install...
Running build script...
ERROR: Command failed with exit code 2:
Output:
devin-agent-sample@1.0.0 build
tsc
src/index.ts(12,35): error TS7016: Could not find a declaration file for module 'express'. 'C:/Users/myusername/Downloads/WorkPlace/A365/devin/sample-agent/node_modules/express/index.js' implicitly has an 'any' type.
Try npm i --save-dev @types/express if it exists or add a new declaration (.d.ts) file containing declare module 'express';
src/index.ts(36,23): error TS7006: Parameter 'err' implicitly has an 'any' type.
ERROR: Deployment failed: [NODE_BUILD_FAILED] Failed to build the Node.js project using 'npm run build'.
- Project directory: C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent
ERROR: App Deployment failed
Deployment failed: [NODE_BUILD_FAILED] Failed to build the Node.js project using 'npm run build'.
- Project directory: C:\Users\myusername\Downloads\WorkPlace\A365\devin\sample-agent
Please review the logs and retry the deployment
For more details, see the log file at: C:\Users\myusername\AppData\Local\Microsoft.Agents.A365.DevTools.Cli\logs\a365.deploy.log
Expected behavior
It should run successfully.
SDK Version
Latest: 1.1.104-preview
Language/Runtime
Node 24.14.0
OS
Windows 11
How to Reproduce
1.Clone the repo
2.Setup the Devin Sample
3.npm i
4.a365 config init
5.a365 setup all
Output
No response
Screenshots
No response
Code of Conduct
- I agree to follow the Microsoft Open Source Code of Conduct.
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
Reproduce the failure from the Devin sample with npm i, a365 config init, a365 setup all, and a365 deploy on Windows 11. Start with src/index.ts and the referenced a365 deployment log, then verify that npm run build completes and deployment succeeds without the reported dependency or TypeScript errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, nodejs, typescript
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100