Our deployments (using latest v1.5.1) just started failing with error message Cannot find module './debug'. These were working with the prior release. Here is the full output of the GitHub Action deployment:
node:internal/modules/cjs/loader:1031
throw err;
^
Error: Cannot find module './debug'
Require stack:
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\debug\src\node.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\debug\src\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\https-proxy-agent\dist\agent.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\https-proxy-agent\dist\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\@azure\core-rest-pipeline\dist\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\@azure\core-client\dist\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\@azure\arm-storage\dist\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\lib\publishers\websiteRunFromPackageDeploy.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\lib\publishers\index.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\lib\handlers\contentPublisher.js
- C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\lib\main.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1028:15)
at Function.Module._load (node:internal/modules/cjs/loader:873:27)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at require (node:internal/modules/cjs/helpers:108:18)
at Object.<anonymous> (C:\actions-runner\digital-runner-05\_work\_actions\Azure\functions-action\v1\node_modules\debug\src\node.js:14:28)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Module.require (node:internal/modules/cjs/loader:1100:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\debug\\src\\node.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\debug\\src\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\https-proxy-agent\\dist\\agent.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\https-proxy-agent\\dist\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\@azure\\core-rest-pipeline\\dist\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\@azure\\core-client\\dist\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\node_modules\\@azure\\arm-storage\\dist\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\lib\\publishers\\websiteRunFromPackageDeploy.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\lib\\publishers\\index.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\lib\\handlers\\contentPublisher.js',
'C:\\actions-runner\\digital-runner-05\\_work\\_actions\\Azure\\functions-action\\v1\\lib\\main.js'
]
}
Changing our workflow to force usage of v1.5.0 has allowed deployments to start again.
Our deployments (using latest v1.5.1) just started failing with error message
Cannot find module './debug'
. These were working with the prior release. Here is the full output of the GitHub Action deployment:Changing our workflow to force usage of v1.5.0 has allowed deployments to start again.