Web app deployment failure

Hi Grace Tong,

Since you're deploying on Azure App Service, you likely don't have the permissions to modify system settings like the inotify file watcher limit. The "npm ERR! nospc" error occurs because the system is trying to watch more files than allowed.

In this environment, you can resolve the issue by optimizing your project. Consider excluding non-critical directories such as node_modules from file monitoring, or adjust your build/watch configurations to limit the number of files being observed. This approach helps prevent exceeding the file watcher limit and avoids triggering the error.

Identify which file-watching tools your project uses. For instance, if your project uses nodemon, you can create or update the nodemon.json configuration file to ignore directories that aren’t essential for monitoring, such as node_modules and dist. Similarly, if you’re using webpack, you can adjust the watchOptions in your webpack configuration to ignore certain paths. These changes help reduce the total number of files being monitored, thereby staying within the allowed limit.

It’s important to review your project structure and remove or exclude any non-critical directories that do not require file watching, such as temporary files, logs, or build artifacts. Testing your application locally after these adjustments ensures that the error is resolved and that the file watcher settings are optimized before deploying the changes.
check your service plan tier - lower tiers have storage limitations.
ensure that your environment meets the requirements for deploying your web app, as limited resources can lead to deployment failures.
https://azureossd.github.io/2023/04/11/troubleshooting-no-space-left-on-device/index.html

If you have any further assistant, do let me know.