node-inspect | Code that 's now part of node , previously node debug | Code Inspection library

I am working to deploy an SSR nuxt app through azure.

When I run yarn build and yarn start locally, it works fine.

The pipeline is correctly building and sending the files over correctly.

I am copying over the file through the pipeline, then unzipping them.

I use Windows Server Standard 2019 to host an Angular 11 Universal with ASP.net Core 3.1.1 website. The website was working great until a server restart. I did many tests to make sure there is no memory leak or some error from the angular app and everything is absolutely perfect. Then I had to restart the server to install some windows updates and then the website was not working anymore. It does an infinite loading.

The thing is if I kill the Node.js JavasScript Runtime running in Background processes which run after the server has restarted and immediately refresh the website, Node will launch a new process and the website will works as expected until the next server restart. I made many other tests to found that specific case scenario.

So, I am not sure how to solve this. Naturally, I want the website to work immediately after a server restart without any intervention from my side. Here are the files and configurations I guess should help to aim the problem, let me know if you need other info:

Website the folder structure:

• dist (folder)
• iisnode (folder)
• main.js
• node_start.cmd
• Web.config

I installed nodejs 14.16.0 LTS first then 15.11.0 Current and also Url Rewrite 2.1 and iisnode-full-v0.2.21-x64

The IIS is version 10. I tried setting the Application Pools to:

• Start application pool immediately
• Start mode: AlwaysRunning
• Idle Time-out Action: Suspend
• Maximum Worker Processus: 0
• Preload Enabled: True

I repeat the website works as expected when I kill the Node.js JavasScript Runtime in the background which run after the server has restarted and then hit refresh to reach the website. Finally, the website works with a valid SSL certificate.

Here the content of node_start.cmd

cd "C:\inetpub\wwwroot\championstogether" "C:\Program Files\nodejs\node.exe" "C:\inetpub\wwwroot\championstogether\main.js"

Then the Web.config

I use node inspect on my js.file but always get:

I installed my React app on Azure App Services using the App Services extension in VS Code. IT said it has successfully installed. I had some issues and had to set a default document of index.js in the web.config to avoid a well-known issue with NodeJs and App Services. However, when I hit the main url of my app, I get back the index.js served back to me a static file. It does not execute the file and render my app, as I expect it to. I have checked via my Kudu's debug console and the Node and npm are installed. The correct versions of them, in fact. I have sat with this issue for 2 whole days and cannot get the app to run.

We have a very stateful NodeJS based web server (Meteor) that occasionally, randomly becomes slow in production. The problem is not reproducible in any of our tests, and we don't know what's triggering it.

To diagnose this, we are using the v8-profiler package. This lets us trigger a 10-second CPU profile and download it for offline analysis.

Despite not having received any commits in 3 years, the package used to work fairly well. It has given us compilation trouble in the past, and now it looks like it stopped compiling entirely, breaking our build. The build happens inside a Docker container with all versions pinned, including NodeJS and v8-profiler itself, so it's unlikely that we can fix this on our end.

I'm thinking there must be some alternative, better maintained approach. But where is it?

(Note that restarting the server with additional flags (like --profile) is not an option, because it destroys all the evidence of the problem.)