Deployment error

[AshleyZhao]

Hi,

We were working away on our project when deploying our project causes the following error:

In the logs, it says npm has trouble finding the package.json file. However, we did not modify any part of that particular path or the content.

0 verbose cli /usr/local/share/nvm/versions/node/v16.20.2/bin/node /usr/local/share/nvm/versions/node/v16.20.2/bin/npm
1 info using [email protected]
2 info using [email protected]
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 2ms
5 timing config:load:file:/usr/local/share/nvm/versions/node/v16.20.2/lib/node_modules/npm/npmrc Completed in 3ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 1ms
8 timing config:load:env Completed in 0ms
9 timing config:load:file:/workspaces/azure-search-openai-demo/app/.npmrc Completed in 1ms
10 timing config:load:project Completed in 5ms
11 timing config:load:file:/home/vscode/.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:/usr/local/share/nvm/versions/node/v16.20.2/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:credentials Completed in 1ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 14ms
19 timing npm:load:configload Completed in 14ms
20 timing npm:load:mkdirpcache Completed in 0ms
21 timing npm:load:mkdirplogs Completed in 1ms
22 verbose title npm run build
23 verbose argv "run" "build"
24 timing npm:load:setTitle Completed in 1ms
25 timing config:load:flatten Completed in 2ms
26 timing npm:load:display Completed in 3ms
27 verbose logfile logs-max:10 dir:/home/vscode/.npm/_logs
28 verbose logfile /home/vscode/.npm/_logs/2024-02-10T21_28_22_774Z-debug-0.log
29 timing npm:load:logFile Completed in 4ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 0ms
32 timing npm:load Completed in 24ms
33 silly logfile start cleaning logs, removing 1 files
34 timing command:run Completed in 2ms
35 verbose stack Error: ENOENT: no such file or directory, open '/workspaces/azure-search-openai-demo/app/package.json'
36 verbose cwd /workspaces/azure-search-openai-demo/app
37 verbose Linux 6.2.0-1018-azure
38 verbose node v16.20.2
39 verbose npm  v8.19.4
40 error code ENOENT
41 error syscall open
42 error path /workspaces/azure-search-openai-demo/app/package.json
43 error errno -2
44 error enoent ENOENT: no such file or directory, open '/workspaces/azure-search-openai-demo/app/package.json'
45 error enoent This is related to npm not being able to find a file.
45 error enoent
46 verbose exit -2
47 timing npm Completed in 37ms
48 verbose code -2
49 error A complete log of this run can be found in:
49 error     /home/vscode/.npm/_logs/2024-02-10T21_28_22_774Z-debug-0.log

Any suggestions on this? Many thanks.

• Also we did revert to older commits when the deployment worked for certain, but the same issue occurs.
• We are running this in a codespace.

[pamelafox]

Hm, can you confirm your azure.yaml matches this one exactly?

https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/azure.yaml

If so, then it should be cd'ing into app/frontend, and looking for the package.json there:
https://github.com/Azure-Samples/azure-search-openai-demo/tree/main/app/frontend

For some reason, it's not cd'ing into frontend, so I wonder if the azure.yaml prepackage hook got changed accidentally.

[IainD925]

@AshleyZhao I had problems deploying into a subscription which had policies enabled. I applied exceptions at the resource group level which resolved the issue.