ENOENT after publishing to Azure

1
votes

I'm really hoping someone can shed some light on what is going on here.

I am publishing to Azure an Angular 7 / .Net Core 2 application. I am using the provided Azure publish profile in Visual Studio.

The application works perfectly fine when I run it locally. Upon deployment, I am seeing a string of error messages, mostly from npm regarding the package.json file.

An unhandled exception occurred while processing the request. AggregateException: One or more errors occurred. (One or more errors occurred. (The NPM script 'start' exited without indicating that the Angular CLI was listening for requests. The error output was: npm ERR! Error: ENOENT, open 'D:\home\site\wwwroot\ClientApp\node_modules\start\package.json'

npm ERR! { [Error: ENOENT, open 'D:\home\site\wwwroot\ClientApp\node_modules\start\package.json']

npm ERR! errno: 34,

npm ERR! code: 'ENOENT',

npm ERR! path: 'D:\home\site\wwwroot\ClientApp\node_modules\start\package.json' }

npm ERR! You may report this log at:

npm ERR! http://github.com/isaacs/npm/issues

npm ERR! or email it to:

npm ERR!

Example of the full stack

2
angularazurenpmasp.net-core-2.0

2 Answers

1
votes

You have to copy all files under the dist/my-app directory to the directory wwwroot of Azure WebApp via Kudu console or FTP . A better approach is to use continuous deployment.

enter image description here

0
votes

I was able to resolve this problem by updating the ancient versions that Azure apparently uses to the latest versions of node that they support.

Here's the ancient versions they had by default:

Default node Azure